From: Antony Pavlov <antonynpavlov@gmail.com>
To: barebox@lists.infradead.org
Cc: Daniele Lacamera <daniele.lacamera@tass.be>
Subject: [RFC] picotcp.20140628
Date: Sat, 28 Jun 2014 18:25:22 +0400 [thread overview]
Message-ID: <20140628182522.f1a434b64c2b01de8c9af6ca@gmail.com> (raw)
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
reply other threads:[~2014-06-28 14:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140628182522.f1a434b64c2b01de8c9af6ca@gmail.com \
--to=antonynpavlov@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=daniele.lacamera@tass.be \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox