From: Daniele Lacamera <daniele.lacamera@tass.be>
To: barebox <barebox@lists.infradead.org>
Subject: Re: [RFC] [WIP] incorporate picotcp into barebox: a small demo
Date: Mon, 26 May 2014 11:35:18 +0200 [thread overview]
Message-ID: <CAOngqVXKEWNabzwCbYg_AXiy95Mzm6BNc7Nr-sNWUyDZ9sX0bA@mail.gmail.com> (raw)
In-Reply-To: <20140525135819.ebfd62810f698e8f13dbf558@gmail.com>
On Sun, May 25, 2014 at 11:58 AM, Antony Pavlov <antonynpavlov@gmail.com> wrote:
> Hi all!
>
> I have adapted barebox for work with picotcp network stack.
>
Hello Antony,
Great news! Thanks for announcing this. Here is a few comments from our side.
I've taken a look at the code. I like the general approach, and it
seems that some functionality could already be replaced with picotcp
modules and components (e.g. ARP, DHCP, DNS.), and some new can easily
be integrated if the project would benefit of some other service
available from cli, such as SLAAC, sNTP, mDNS, DHCP server, etc.
> We need additional effors for adapting barebox and picotcp
> for more easy joint operation.
Regarding this, we would like to help with a cleaner integration, so
feel free to submit requests in the form of "issues" on our github if
you need to introduce new pico_err's, or any suggestion you might have
regarding the APIs for the standalone tool support.
The whole PicoTCP team is very enthusiast about what you guys started,
and we keep ourselves at your disposal for whatever you might need
from our side.
I have to add, it is possibly interesting for barebox community, we
recently added the support for blocking sockets with a POSIX-compliant
API, which would make socket development much easier if properly
connected to the execution model. You might want to have a look at
this repository we just created:
https://github.com/tass-belgium/picotcp-bsd
Last but not least, I would love to see some ipv6 integration, as soon
as your interface is in the expected status, I could try and add the
support for ipv6 addresses and routing myself, even if I don't know
what are the plans of barebox regarding this.
Kudos to you all for this great initiative, and a special "thank you"
to Alessandro for endorsing our free TCP/IP stack :)
Have a nice day
--
Daniele Lacamera
Senior Software Architect
TASS.BE - Part of Altran
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2014-05-26 9:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-25 9:58 Antony Pavlov
2014-05-26 9:35 ` Daniele Lacamera [this message]
2014-05-26 9:45 ` Lucas Stach
2014-05-26 12:09 ` Antony Pavlov
2014-05-27 5:30 ` Sascha Hauer
2014-05-27 7:52 ` Daniele Lacamera
2014-05-27 9:46 ` Daniele Lacamera
2014-05-27 14:04 ` Antony Pavlov
2014-05-27 17:26 ` Daniele Lacamera
2014-05-29 5:40 ` Antony Pavlov
2014-05-28 6:08 ` Sascha Hauer
2014-05-28 7:23 ` Juergen Borleis
2014-05-28 10:32 ` Antony Pavlov
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=CAOngqVXKEWNabzwCbYg_AXiy95Mzm6BNc7Nr-sNWUyDZ9sX0bA@mail.gmail.com \
--to=daniele.lacamera@tass.be \
--cc=barebox@lists.infradead.org \
/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