From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31318 invoked by alias); 3 May 2013 08:49:34 -0000 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 Received: (qmail 31306 invoked by uid 89); 3 May 2013 08:49:33 -0000 X-Spam-SWARE-Status: No, score=1.0 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED autolearn=ham version=3.3.1 Received: from inthemill.ch (HELO mail.inthemill.ch) (178.63.89.201) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Fri, 03 May 2013 08:49:18 +0000 Received: from localhost (localhost [127.0.0.1]) by mail.inthemill.ch (Postfix) with ESMTP id D2E184A40AA; Fri, 3 May 2013 10:49:15 +0200 (CEST) Received: from mail.inthemill.ch ([127.0.0.1]) by localhost (belele.inthemill.ch [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uKuS7w09-S2R; Fri, 3 May 2013 10:49:13 +0200 (CEST) Received: from Simons-MacBook-Pro-2.local (5-172-129-222.dyn.cable.fcom.ch [5.172.129.222]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: simon.kallweit@intefo.ch) by mail.inthemill.ch (Postfix) with ESMTPSA id 855134A409A; Fri, 3 May 2013 10:49:13 +0200 (CEST) Message-ID: <51837A0A.2030909@intefo.ch> Date: Fri, 03 May 2013 08:49:00 -0000 From: Simon Kallweit User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130328 Thunderbird/17.0.5 MIME-Version: 1.0 To: John Dallaway CC: Will Wagner , eCos development list Subject: Re: Updating lwip References: <518160EE.7090602@carallon.com> <51829465.5000605@dallaway.org.uk> In-Reply-To: <51829465.5000605@dallaway.org.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2013-05/txt/msg00003.txt.bz2 Hi Will, Hi John, I'm not actively using eCos anymore since about three years, when I quit my job as an embedded developer and started studying computer science. I just thought I'd give a shout so you know. As far as I can remember, the changes in the PPP codebase were primarily to get PPP running in sequential (non-threaded) mode, as the code in 1.3 was not fit for the task and we used eCos on a pretty limited platform where we did not want to afford the overhead of using lwIP in threaded mode. Also there might have been some additions to allow writing PPP dumps in order to debug connection traces in wireshark, but I'm not a 100% sure if that was commited to the eCos repository at all. In lwIP 1.4 I think they refactored the PPP code to allow for proper handling in sequential mode, so my hacks would get obsolete. I remember that I have started porting a 1.4 release candidate back then, but never finished the port. I can dig out the sources if this is of any help, but maybe it's simpler to just go from the current lwIP release. Just let me know .. Best regards, Simon On 5/2/13 6:29 PM, John Dallaway wrote: > Hi Will > > I am sure an upgrade of the eCos lwIP stack to the latest stable > upstream release would be welcomed by many eCos users. > > On 01/05/13 19:37, Will Wagner wrote: > >> Have started looking at the difference between upstream 1.3.2 and what >> is check in to ecos. There are quite a lot of differences, although most >> of them are trivial renaming. >> >> Does anyone know what changes were made to the lwip source and why. In >> particular lost of the ppp code has had functions and variables renamed. > The lwIP PPP code currently checked-in to the eCos repository was > contributed by Simon Kallweit. This would explain the substantial > PPP-related changes in your code comparison. It was always the intention > to migrate to the official lwIP PPP sources over time. Ref: > > http://ecos.sourceware.org/ml/ecos-discuss/2010-01/msg00057.html > > As with all imports, it is important to minimise changes to the upstream > code as far as possible. That way, future imports become much easier. > > John Dallaway > eCos maintainer > http://www.dallaway.org.uk/john