Hi Gustavo Denardin,
>>Are you interested in helping us?
Personally, I am interested – it should be FUN.
So you may write me directly to Andrey.Butok@freescale.com.
BTW:
>>The most important is to make FNET event driver
The FNET TCP/IP stack is interrupt-driven (Ethernet RX and Timer (100ms period)).
>> cause in the way it is now, FNET occupies all the remainder CPU
I guess you mean user applications using FNET.
So it is fully up to applications how to occupy the CPU.
For example, you may call fnet_ poll() ( should be renamed to fnet_services_poll() ),
that handles provided FNET application layer severs/clients, not in simple loop but with some delay/timeout.
Or maybe even better, we can add RTOS-specific event(s) (on new connection, new data in socket buffer etc.),
that will wake up a waiting/sleeping application.
Thanks,
Andrey Butok