From: John Dallaway <john@dallaway.org.uk>
To: Will Wagner <will_wagner@carallon.com>
Cc: eCos development list <ecos-devel@sourceware.org>,
Simon Kallweit <simon.kallweit@intefo.ch>
Subject: Re: Updating lwip
Date: Thu, 02 May 2013 16:29:00 -0000 [thread overview]
Message-ID: <51829465.5000605@dallaway.org.uk> (raw)
In-Reply-To: <518160EE.7090602@carallon.com>
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
next prev parent reply other threads:[~2013-05-02 16:29 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 [this message]
2013-05-03 8:49 ` Simon Kallweit
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51829465.5000605@dallaway.org.uk \
--to=john@dallaway.org.uk \
--cc=ecos-devel@sourceware.org \
--cc=simon.kallweit@intefo.ch \
--cc=will_wagner@carallon.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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).