From: Antony Pavlov <antonynpavlov@gmail.com>
To: DI PEDE Michele <michele.dipede@altran.com>
Cc: barebox <barebox@lists.infradead.org>,
LACAMERA Daniele <daniele.lacamera@altran.com>
Subject: Re: picotcp barebox integration
Date: Tue, 31 Mar 2015 15:50:51 +0300 [thread overview]
Message-ID: <20150331155051.5c09f9d591bd04b84423232d@gmail.com> (raw)
In-Reply-To: <66FFD9910051464CB128685455FE423D2FB77B@XMB-DCFR-31.europe.corp.altran.com>
Hi!
I have just published latest picotcp-enabled barebox.
Please see my picotcp.20150331 branch in my github barebox repo
(https://github.com/frantony/barebox/tree/picotcp.20150331).
This version is based on latest barebox-next and latest picotcp-development.
Here is barebox picotcp network features:
* network interfaces and the 'ifconfig' command to rule them;
* the 'route' command to see current picotcp route table;
* the 'picoping' command to use picotcp ping support (also now barebox responds
to ping requests);
* the 'dhclient' command to use picotcp dhcp client;
(new) * picotcp-based tftp filesystem support.
Here is note/todo list:
1. tftp write operation is not supported;
2. with picotcp we can't easely use 'tftp' command with old syntax
(no $<current ethernet>.serverip anymore);
3. just now picotcp-based tftp file transfer is 5 times slower than
old realisation (partialy it is my bad, e.g. extra memory copy operation
is used for code simplification);
4. picotcp has dns support, but just now it is unused in barebox;
5. no nfs support in picotcp (should we can keep current barebox nfs support on
top of barebox UDP support?).
--
Best regards,
Antony Pavlov
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2015-03-31 12:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-21 14:25 Antony Pavlov
2014-11-28 19:38 ` Daniele Lacamera
2014-12-19 17:28 ` Michele Di Pede
2015-01-28 13:35 ` DI PEDE Michele
2015-02-28 17:01 ` Antony Pavlov
2015-03-01 0:29 ` DI PEDE Michele
2015-03-01 12:54 ` Antony Pavlov
2015-03-01 16:15 ` DI PEDE Michele
2015-03-31 12:50 ` Antony Pavlov [this message]
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=20150331155051.5c09f9d591bd04b84423232d@gmail.com \
--to=antonynpavlov@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=daniele.lacamera@altran.com \
--cc=michele.dipede@altran.com \
/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