From: Will Wagner <will_wagner@carallon.com>
To: "ecos-devel@ecos.sourceware.org" <ecos-devel@ecos.sourceware.org>
Subject: Updating lwip
Date: Wed, 01 May 2013 18:38:00 -0000 [thread overview]
Message-ID: <518160EE.7090602@carallon.com> (raw)
We are interested in updating to lwip 1.4.1. Has anyone already done any
work on this?
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.
Any pointers for the porting process much appreciated.
Thanks
Will
--
------------------------------------------------------------------------
Will Wagner will_wagner@carallon.com
Development Manager Office Tel: +44 (0)20 7371 2032
Carallon Ltd, Studio G20, Shepherds Building, Rockley Rd, London W14 0DA
------------------------------------------------------------------------
next reply other threads:[~2013-05-01 18:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-01 18:38 Will Wagner [this message]
2013-05-02 13:19 ` Michael Jones
2013-05-02 16:29 ` John Dallaway
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=518160EE.7090602@carallon.com \
--to=will_wagner@carallon.com \
--cc=ecos-devel@ecos.sourceware.org \
/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).