> On Mon, Jun 2, 2014 at 10:38 AM, Sascha Hauer wrote:
>> How I see it pico_icmp4_ping should return the cookie so that a ping
>> abort function can be implemented:
>>
>> void pico_icmp4_ping_abort(struct pico_icmp4_ping_cookie *cookie)
Hello Sascha, et al.
PicoTCP now supports abort operations
On Mon, Jun 2, 2014 at 10:38 AM, Sascha Hauer wrote:
> On Fri, May 30, 2014 at 01:14:08PM +0400, Antony Pavlov wrote:
> This must be solved in the pico_icmp4.c code. The counterpart of
> pico_tree_insert (pico_tree_delete?) must be called as an response to
> ctrlc().
>
> How I see it pico_icmp4_pi
On Fri, May 30, 2014 at 01:14:08PM +0400, Antony Pavlov wrote:
> Picotcp tends to work in an asynchronious way.
>
> E.g. for ping we have to use "pico_icmp4_ping()"
> (to start ping task) and the special icmp4 handler
> (callback function) "cb_ping()".
>
> But the ping command in barebox works in
> Has anybody any ideas how to improve the situation?
AFAIK barebox doesn't have the concept of aborting something. e.g. you
cannot do "msleep 2" and then press Ctrl-C. The you
see when you press Ctrl-C is from hush, and it is internal to hush.c
(see struct in_str, member interrupt).
___
Picotcp tends to work in an asynchronious way.
E.g. for ping we have to use "pico_icmp4_ping()"
(to start ping task) and the special icmp4 handler
(callback function) "cb_ping()".
But the ping command in barebox works in very simple
way:
* user types 'ping ' in the barebox shell command line;
