From: John Dallaway <john@dallaway.org.uk>
To: Simon Kallweit <simon.kallweit@intefo.ch>
Cc: eCos development list <ecos-devel@ecos.sourceware.org>
Subject: lwIP 1.4.0 port planning [ was Re: lwip 1.3.2 port ]
Date: Sun, 08 May 2011 08:11:00 -0000 [thread overview]
Message-ID: <4DC64814.90701@dallaway.org.uk> (raw)
In-Reply-To: <4B5DC7C4.407@intefo.ch>
Hi Simon
Simon Kallweit wrote:
> Over the weekend I did initial work of an lwIP
> 1.4.x port. I think by the time of an official 1.4.x release, I will be
> able to provide an updated port for eCos. In the meantime, people can
> use the 1.3.2 port.
lwIP 1.4.0 has now been released, rather later than I had anticipated.
Are you still active with lwIP and interested in working on an update
for the eCos repository? It would be helpful to know your current
thoughts on this. There may be others in the community who could lend
support to the update and/or testing.
John Dallaway
eCos maintainer
http://www.dallaway.org.uk/john
next prev parent reply other threads:[~2011-05-08 8:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <73f9997f0907192203h77494e62u58b44ccfc7a738f4@mail.gmail.com>
[not found] ` <4A65B8AE.8090204@martinlaabs.de>
[not found] ` <73f9997f0907212153i743cfc7as86d2a1205c5dc7ab@mail.gmail.com>
[not found] ` <73f9997f0907220421y145a62c3lb2728a132474c900@mail.gmail.com>
[not found] ` <4A66F7E0.4050703@intefo.ch>
[not found] ` <73f9997f1001220342h7bc1c79cl7180a184bee867f3@mail.gmail.com>
2010-01-22 12:54 ` lwip 1.3.2 port Simon Kallweit
2010-01-22 13:31 ` John Dallaway
2010-01-22 14:43 ` Simon Kallweit
2010-01-22 18:51 ` John Dallaway
2010-01-23 11:57 ` Simon Kallweit
2010-01-23 14:04 ` John Dallaway
2010-01-23 15:46 ` Simon Kallweit
2010-01-25 11:44 ` John Dallaway
2010-01-25 16:35 ` Simon Kallweit
2011-05-08 8:11 ` John Dallaway [this message]
2011-06-07 20:28 ` lwIP 1.4.0 port planning [ was Re: lwip 1.3.2 port ] Ilija Kocho
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=4DC64814.90701@dallaway.org.uk \
--to=john@dallaway.org.uk \
--cc=ecos-devel@ecos.sourceware.org \
--cc=simon.kallweit@intefo.ch \
/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).