* [RFC] picotcp.20140628
@ 2014-06-28 14:25 Antony Pavlov
0 siblings, 0 replies; only message in thread
From: Antony Pavlov @ 2014-06-28 14:25 UTC (permalink / raw)
To: barebox; +Cc: Daniele Lacamera
Hi All!
I have pushed new version of picotcp-enabled barebox to github:
https://github.com/frantony/barebox/commits/picotcp.20140628
Changes since picotcp.20140530:
* rebase over latest barebox and picotcp
* net: make 'picoping' behave like traditional 'ping' command
use pico_icmp4_ping_abort()
* net: make 'dhclient' behave like old 'dhcp' command
use pico_dhcp_client_abort()
There is a problem with picoping.
If I start picoping and no correct reply packet is received
then picoping ends with timeout error message. (good!)
But if I start picoping and only several reply packets are
received (e.g. I intentionaly break network interface setup)
but not the last then timeout callback function is not called.
--
Best regards,
Antony Pavlov
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2014-06-28 14:13 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-06-28 14:25 [RFC] picotcp.20140628 Antony Pavlov
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox