mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Daniele Lacamera <daniele.lacamera@tass.be>
To: Antony Pavlov <antonynpavlov@gmail.com>
Cc: barebox <barebox@lists.infradead.org>, PicoTCP <picotcp@tass.be>,
	Frederik Van Slycken <frederik.van.slycken@gmail.com>
Subject: Re: [RFC] incorporate picotcp into barebox
Date: Tue, 24 Jun 2014 09:36:29 +0200	[thread overview]
Message-ID: <CAOngqVX56ZS=KgWJs0x6yS_jxNewYaWaTX-Lqvmk-25xBs+d4g@mail.gmail.com> (raw)
In-Reply-To: <20140624101809.3e4e5ed94246bea99f2d622c@gmail.com>

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

      reply	other threads:[~2014-06-24  7:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-24  6:18 Antony Pavlov
2014-06-24  7:36 ` Daniele Lacamera [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='CAOngqVX56ZS=KgWJs0x6yS_jxNewYaWaTX-Lqvmk-25xBs+d4g@mail.gmail.com' \
    --to=daniele.lacamera@tass.be \
    --cc=antonynpavlov@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=frederik.van.slycken@gmail.com \
    --cc=picotcp@tass.be \
    /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