Re: [lwip-users] best approach to lwip using FreeRTOS

[Francois Bouchard]

Hi,

If you are used to the raw API, I suggest to continue with it.  The raw API
takes a bit less RAM, and its a bit faster than the other two APIs.  As an
example,  with  the raw API and a OS (FreeRTOS in your case, and mine too!)
you can implement an echo server with only 2 tasks:

1) an Ethernet task that receive/manage Rxed frames
2) and the core TCP/IP thread

Francois


----- Original Message -----
From: "Sergio Sider" <address@hidden>
To: "Mailing list for lwIP users" <address@hidden>
Sent: Friday, March 13, 2009 7:01 AM
Subject: [lwip-users] best approach to lwip using FreeRTOS


> Hi guys,
>
> I posted this message on the FreeRTOS list and they suggested me to
> post it here...
> here it goes:
>
> Hi all,
>
> I need an opinion:
>
> I am used to lwip raw interface, and like it´s simplicity and callback
> approach.
>
> For years, I was using in my embedded programs, a simple cooperative
> "multitasking" interface, where I call all tasks sequentially in the
> main loop, using a simple ticker.
>
> I am now starting to try FreeRTOS...
>
> What´s the best way to use lwip ?
> Continue to use raw api (I suppose I have to do it inside one single
> task)? or start using netcon to take advantage of the multitasking?
>
> I know the answer might depend on the complexity of my design, but is
> one approach way better than the other so I just should not think
> about it ?
>
> Thanks for any advice!
> Sergio P. Sider
>
>
> _______________________________________________
> lwip-users mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/lwip-users
>