From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4625 invoked by alias); 3 May 2013 08:55:46 -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 4612 invoked by uid 89); 3 May 2013 08:55:46 -0000 X-Spam-SWARE-Status: No, score=-1.5 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED autolearn=ham version=3.3.1 Received: from mail.carallon.com (HELO mail.carallon.com) (95.177.28.122) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Fri, 03 May 2013 08:55:45 +0000 X-MDAV-Result: clean X-MDAV-Processed: mail.carallon.com, Fri, 03 May 2013 09:55:42 +0100 Received: from [172.20.1.8] by mail.carallon.com (Cipher TLSv1:-SHA:128) (MDaemon PRO v13.0.5) with ESMTP id md50001272646.msg for ; Fri, 03 May 2013 09:55:41 +0100 X-Spam-Processed: mail.carallon.com, Fri, 03 May 2013 09:55:41 +0100 (not processed: message from trusted or authenticated source) X-MDRemoteIP: 172.20.1.8 X-Return-Path: will_wagner@carallon.com X-Envelope-From: will_wagner@carallon.com X-MDaemon-Deliver-To: ecos-devel@sourceware.org Message-ID: <51837B89.5060708@carallon.com> Date: Fri, 03 May 2013 08:55:00 -0000 From: Will Wagner User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130328 Thunderbird/17.0.5 MIME-Version: 1.0 To: Simon Kallweit CC: John Dallaway , eCos development list Subject: Re: Updating lwip References: <518160EE.7090602@carallon.com> <51829465.5000605@dallaway.org.uk> <51837A0A.2030909@intefo.ch> In-Reply-To: <51837A0A.2030909@intefo.ch> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2013-05/txt/msg00004.txt.bz2 Hi Simon & John, Thanks for the feedback, it is useful for understanding the existing changes. So our plan for updating is as follows: - move files according to ecos scheme. This is pretty straight forward, a number of files are moved and the ipv6 code (that doesn't work) is removed. - drop all ppp changes and go with vanilla 1.4.1 ppp implementation - drop lwip tests and keep the current ecos ones - apply patches/changes made to 1.3.2 for ecos and all patches since to 1.4.1 - follow upgrading instructions for lwip. This will involve a few new cdl options and changing a few functions. After that is will just work :) No idea how long this is going to take and it's not our top priority, fitting it in when we get the chance. Will post some patches once we have some progress. Regards Will On 03/05/2013 09:49, Simon Kallweit wrote: > 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 > -- ------------------------------------------------------------------------ Will Wagner will_wagner@carallon.com Development Manager Office Tel: +44 (0)20 7471 9224 Carallon Ltd, Studio G20, Shepherds Building, Rockley Rd, London W14 0DA ------------------------------------------------------------------------