From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32381 invoked by alias); 4 Apr 2009 14:54:04 -0000 Received: (qmail 32373 invoked by uid 22791); 4 Apr 2009 14:54:03 -0000 X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from mtaout02-winn.ispmail.ntl.com (HELO mtaout02-winn.ispmail.ntl.com) (81.103.221.48) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 04 Apr 2009 14:53:58 +0000 Received: from aamtaout01-winn.ispmail.ntl.com ([81.103.221.35]) by mtaout02-winn.ispmail.ntl.com (InterMail vM.7.08.04.00 201-2186-134-20080326) with ESMTP id <20090404145355.PJMP4080.mtaout02-winn.ispmail.ntl.com@aamtaout01-winn.ispmail.ntl.com>; Sat, 4 Apr 2009 15:53:55 +0100 Received: from cog.dallaway.org.uk ([86.9.207.237]) by aamtaout01-winn.ispmail.ntl.com (InterMail vG.2.02.00.01 201-2161-120-102-20060912) with ESMTP id <20090404145355.LDXT13254.aamtaout01-winn.ispmail.ntl.com@cog.dallaway.org.uk>; Sat, 4 Apr 2009 15:53:55 +0100 Received: from cog.dallaway.org.uk (cog.dallaway.org.uk [127.0.0.1]) by cog.dallaway.org.uk (8.13.8/8.13.8) with ESMTP id n34Erq1v012811; Sat, 4 Apr 2009 15:53:52 +0100 Message-ID: <49D77480.7040408@dallaway.org.uk> Date: Sat, 04 Apr 2009 14:54:00 -0000 From: John Dallaway User-Agent: Thunderbird 2.0.0.19 (X11/20090107) MIME-Version: 1.0 To: John Eigelaar , Simon Kallweit CC: eCos development list Subject: Re: lwIP References: <4926E654.2050302@barda.agala.net> <4926E76F.70307@intefo.ch> <4926EBF8.5060708@intefo.ch> <492710C2.1050708@mindspring.com> <1227539519.4641.40.camel@janet> In-Reply-To: <1227539519.4641.40.camel@janet> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Mailing-List: contact ecos-devel-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: ecos-devel-owner@ecos.sourceware.org X-SW-Source: 2009-04/txt/msg00000.txt.bz2 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