From: Antony Pavlov <antonynpavlov@gmail.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox <barebox@lists.infradead.org>
Subject: Re: barebox picotcp integration (2015.06.14)
Date: Sat, 20 Jun 2015 14:09:12 +0300 [thread overview]
Message-ID: <20150620140912.b8435aff9de4a645f5d4639e@gmail.com> (raw)
In-Reply-To: <20150617092857.GJ6325@pengutronix.de>
On Wed, 17 Jun 2015 11:28:57 +0200
Sascha Hauer <s.hauer@pengutronix.de> wrote:
> On Mon, Jun 15, 2015 at 01:13:43AM +0300, Antony Pavlov wrote:
> > Hi!
> >
> > I have just published latest picotcp-enabled barebox.
> > Please see my 20150614.picotcp branch in my github barebox repo
> > (https://github.com/frantony/barebox/tree/20150614.picotcp).
> >
...
>
> Why are you using the picotcp tftp implementation? picotcp surely
> supports sending/receiving udp packets, right? Wouldn't it be a good
> first step to replace the barebox udp API with the one picotcp provides?
> I mean I would expect that you replace only the network stack, not the
> network stack including the applications. If at some point we decide
> that the tftp implementation in picotcp is better than the one in
> barebox that would be the time to switch it.
>
I have reworked tftp support: now barebox tftp implementation is used on top
of picotcp udp/ip stack and works 2 times slower than original u-boot stack-based
implementation (I have tested it with sandbox arch).
Please see draft tftp commit here: https://github.com/frantony/barebox/tree/20150620.picotcp
I'll try to switch barebox nfs support to picotcp udp/ip in several days.
--
Best regards,
Antony Pavlov
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2015-06-20 11:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-14 22:13 Antony Pavlov
2015-06-17 9:28 ` Sascha Hauer
2015-06-20 11:09 ` Antony Pavlov [this message]
2015-06-22 6:00 ` Sascha Hauer
2015-06-24 6:11 ` Antony Pavlov
2015-06-26 9:54 ` Sascha Hauer
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=20150620140912.b8435aff9de4a645f5d4639e@gmail.com \
--to=antonynpavlov@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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