Re: lwIP

[Simon Kallweit <simon dot kallweit at intefo dot ch>]

John Dallaway wrote:
> Hi John and Simon
>
> John Eigelaar wrote:
>
>   
> > On Fri, 2008-11-21 at 14:49 -0500, Frank Pagliughi wrote:
> >     
> > > Simon Kallweit wrote:
> > >       
> > > > Simon Kallweit wrote:
> > > >         
> > > > > Frank J. Beckmann wrote:
> > > > >           
> > > > > > Hello,
> > > > > >
> > > > > > are there plans for updating eCos' lwIP port to a more recent version?
> > > > > >             
> > > > I just had a quick look of the lwIP in the current ECOS version. It 
> > > > differs just very slightly from the actual lwIP 1.1.1 release, not 
> > > > many changes. I guess an update to a more recent lwIP version should 
> > > > be pretty simple and straight forward. I'll start working on it in 
> > > > around a week, have to get my GSM modem working first :)
> > > >
> > > >         
> > I have been trying on and off tp port lwip 1.3.0 to ecos. The current
> > version has a serious memory leak when under fire and also does not
> > honor the backlog parameter for lwip_listen and lwip_accept mechanisms.
> >
> > In 1.3.0 the init part of the lwIP source has been greatly improved and
> > now works well to initialise the lwIP stack but is of course now
> > completely incompatible with the existing eCos port. The sys_arch API
> > has been update as well to counetr the aforementioned memory leaks.
> >
> > I am also not sure what to do really with the IPv6 and IPv4 config
> > options for the lwIP stack.
> >
> > I have compiled the test cases with the new 1.3.0 source but I  still
> > can not get any of them to run on the Linux synth target. Some of it is
> > actualy me learning the synth target as I go along as well as me not
> > really having any time to spend on this other than time set aside out of
> > curiosity.
> >     
>
> I am keen to see lwIP updated in the eCos repository and can offer help
> with the CDL if necessary.
>
> It looks like good progress has been made with lwIP 1.3.0 on eCos
> already. Could you drop a note to this list with the current status of
> your work please and we can plan accordingly?
>
> Given the changes in the lwIP initialisation code, can anyone comment on
> the likely effort to port an eCos application based on the existing eCos
> lwIP stack to lwIP 1.3.0?
>
> lwIP is a good fit for eCos and I can see the use of this stack
> dominating in the future. With this in mind, it would be great to
> support as many features of the stack as possible (including IPv6).
>
> John Dallaway
>   

I just wanted to let you know that I have done an lwip 1.3.0 port for 
our current project too. I haven't committed anything yet as the port is 
not yet finished. I have re-written parts of the CDL, rewritten the 
ethernet driver interface and have a working port using the RAW 
interfaces. The sequential APIs are not yet supported in my port as I 
currently don't need them. I have also done some work on PPP, as we're 
using lwip to run a GPRS modem connection. I also use ethernet via the 
synth target for testing though. PPP is really in quite a horrible state 
and unmaintained in lwip, there is still lots to improve. Unfortunately 
I didn't really had the time for anything serious. I just got it working 
for our particular needs, which basically is just another hack ;)

Anyone interested in my code may have a look at 
http://git.inthemill.ch/?p=ecos.git;a=summary

I think it would be great to update the official lwip port in ecos and 
I'm willing to help where I can.

Simon