[RFC] [WIP] incorporate picotcp into barebox: a small demo

[Daniele Lacamera]

On Sun, May 25, 2014 at 11:58 AM, Antony Pavlov <antonynpavlov at 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