mail archive of the barebox mailing list
 help / color / mirror / Atom feed
* [RFC] incorporate picotcp into barebox
@ 2014-06-24  6:18 Antony Pavlov
  2014-06-24  7:36 ` Daniele Lacamera
  0 siblings, 1 reply; 2+ messages in thread
From: Antony Pavlov @ 2014-06-24  6:18 UTC (permalink / raw)
  To: Daniele Lacamera; +Cc: barebox, Frederik Van Slycken

Hi, Daniele!

Do you have any progress on introducing barebox-related ping and dhcp client
changes into picotcp?

-- 
Best regards,
  Antony Pavlov

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [RFC] incorporate picotcp into barebox
  2014-06-24  6:18 [RFC] incorporate picotcp into barebox Antony Pavlov
@ 2014-06-24  7:36 ` Daniele Lacamera
  0 siblings, 0 replies; 2+ messages in thread
From: Daniele Lacamera @ 2014-06-24  7:36 UTC (permalink / raw)
  To: Antony Pavlov; +Cc: barebox, PicoTCP, Frederik Van Slycken

On Tue, Jun 24, 2014 at 8:18 AM, Antony Pavlov <antonynpavlov@gmail.com> wrote:
> Hi, Daniele!
>
> Do you have any progress on introducing barebox-related ping and dhcp client
> changes into picotcp?
>
> --
> Best regards,
>   Antony Pavlov

Hello Antony,

Yes, I've been working on the components themselves in order to comply
with barebox's CLI requirements. I added a pico_dhcp_client_abort()
function to cancel an ongoing dhcp negotiation, and a
pico_icmp[4|6]_ping_abort() to cancel the ongoing ping operation. All
changes are tested and the new APIs are documented in the user manual.
It is now possible to interrupt ongoing operation (e.g. via CTRL+C
from the barebox CLI).

A fresh manual is created by jenkins after each commit from the .tex
in the source tree and it is avaliable at:
http://162.13.84.104/user_doc.pdf

Additionally, the TFTP branch I created is almost finished: TFTP
client and server are working except for the timeout feature. Due to
our internal quality policy and implement the unit tests with at least
80% coverage in order to qualify for a merge to the master, but
meanwhile both client and server are tested against tftp(d)-hpa. You
can already have a look at the new module:

https://github.com/tass-belgium/picotcp/tree/tftp

In particular, this is how I am testing client/server functionality:
https://github.com/tass-belgium/picotcp/blob/tftp/test/picoapp.c#L2201

Of course before merging there will be a new chapter in the manual
describing the TFTP API.

As usual, comments and suggestions are very welcome.

Regards,

-- 
Daniele Lacamera

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2014-06-24  7:36 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-06-24  6:18 [RFC] incorporate picotcp into barebox Antony Pavlov
2014-06-24  7:36 ` Daniele Lacamera

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox