public inbox for
 help / color / mirror / Atom feed
From: Simon Kallweit <>
To: John Dallaway <>
Cc: Will Wagner <>,
	 eCos development list <>
Subject: Re: Updating lwip
Date: Fri, 03 May 2013 08:49:00 -0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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,

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:
> 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

  reply	other threads:[~2013-05-03  8:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-01 18:38 Will Wagner
2013-05-02 13:19 ` Michael Jones
2013-05-02 16:29 ` John Dallaway
2013-05-03  8:49   ` Simon Kallweit [this message]
2013-05-03  8:55     ` Will Wagner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).