From: Jonathan Larmour <jifl@eCosCentric.com>
To: Simon Kallweit <simon.kallweit@intefo.ch>
Cc: "Frank J. Beckmann" <frank@barda.agala.net>,
"ecos-devel@ecos.sourceware.org"
<ecos-devel@ecos.sourceware.org>
Subject: Re: lwIP
Date: Fri, 21 Nov 2008 19:35:00 -0000 [thread overview]
Message-ID: <49270D3F.7080708@eCosCentric.com> (raw)
In-Reply-To: <4926E76F.70307@intefo.ch>
Simon Kallweit wrote:
> Frank J. Beckmann wrote:
>> Hello,
>>
>> are there plans for updating eCos' lwIP port to a more recent version?
>
> I was planning on doing that, if it's not already planned for the ecos
> 3.0 release. I don't know if eCosCentric has a more up-to-date port.
Sort of. Ours starts from the same original lwIP code base (1.1.0) but I
had to pretty much rewrite Jani's original eCos port as it had a number of
design flaws. It is essentially doomed under load.
But we don't have any plans to release our own port of it, so if you want
an update in the near future, it's not terribly likely to come from
eCosCentric I'm afraid.
Jifl
--
eCosCentric Limited http://www.eCosCentric.com/ The eCos experts
Barnwell House, Barnwell Drive, Cambridge, UK. Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
------["Si fractum non sit, noli id reficere"]------ Opinions==mine
next prev parent reply other threads:[~2008-11-21 19:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-21 16:49 lwIP Frank J. Beckmann
2008-11-21 16:53 ` lwIP Simon Kallweit
2008-11-21 17:12 ` lwIP Simon Kallweit
2008-11-21 19:50 ` lwIP Frank Pagliughi
2008-11-24 15:13 ` lwIP John Eigelaar
2009-04-04 14:54 ` lwIP John Dallaway
2009-04-06 9:44 ` lwIP Simon Kallweit
2009-04-06 10:44 ` lwIP John Eigelaar
2009-04-06 16:46 ` lwIP John Dallaway
2009-04-06 16:59 ` lwIP Simon Kallweit
2009-04-07 7:55 ` lwIP John Dallaway
2009-04-07 8:17 ` lwIP Simon Kallweit
2008-11-21 19:35 ` Jonathan Larmour [this message]
2008-11-21 19:37 ` lwIP Jonathan Larmour
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=49270D3F.7080708@eCosCentric.com \
--to=jifl@ecoscentric.com \
--cc=ecos-devel@ecos.sourceware.org \
--cc=frank@barda.agala.net \
--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).