Lpc2000

>>
>>If you have space issues, uIP is the way to go.  If you don't, then lwIP
>>is more the thing.
> 
> Can anyone with Ethernet Nut/Net experience comment?


<< Apologies in advance for the infomercial, I have no commercial connection,
  just very pleased with the results >>

  I can not comment on the internal IP stack structure of EtherNut beyond saying 
the following:

- EtherNut & it's co-operative RTOS are effective on small footprint embedded 
systems, it started on an 8 bit AVR. It is there & it works with many years of 
history in a broad range of commercial apps.

- The stack uses the single copy of the packet & doesn't copy between layers. 
This is explained in the document "Ethernut Software Manual" on the documents 
page, the link for which is given below.

- It is actively being developed and supported by it's author and user-base.

~ 10 postings per day on forum. The big kids don't poke fun at me when I ask 
dumb noob questions.

- It is functionally documented - http://www.ethernut.de/en/documents/index.html

- Reference hardware is available from the author at www.egnite.de

- It has a configuration system which allows even GNUuoobs such as me to be able 
to readily build it and use it with either GCC or some other commercial compilers.

- In short I can easily run the comprehensive range of examples and make the 
leds flash without too much hair loss. This alone may allow me to get to a point 
where I <can> make intelligent comment about stack internals at a later date.

- The author hasn't done what a number of other open source projects have done & 
used contributors as beta testers before sealing off further open source 
development and going closed commercial... So far ;-)

- There is an ARM7 version but it is currently targeted at an older Atmel 
AT91R40008 ARM device which greatly pre-dates the SAM7 & LPC2xxx

- Another contributor is currently doing an LPC2xxx port but as yet the source 
has not been made available. http://www.usbdip.de/en/ethernut2294/index.html  It 
is built with the crossworks compiler

- Contributors appear to be waiting to see how the cards fall in the latest 
Philips / Atmel ARM based product releases before advancing the ARM port. 
Shouldn't be long however.

- The stack seems to have a consistent, functional community that is generous 
with it's contributions and support. People come and go & have done so for many 
years leaving extra bits on the stack. The stack just slowly gets better. That 
is important if you are going to spend the time getting up to speed with it.

In my particular case with the XNut hardware product which also uses the 
Ethernut stack ( similarly well supported by it's creator www.focus-sw.com )  we 
got from concept to invoiceable application in no time flat & for me that is 
what keeps the customer happy & the family fed.  I eagerly await the new ARM 
based units.

Cheers
Don