From: Paul Beskeen <paulb@ecoscentric.com>
To: Andrew Lunn <andrew.lunn@ascom.ch>
Cc: Simon Kallweit <simon.kallweit@intefo.ch>,
ecos-maintainers@ecos.sourceware.org
Subject: Re: NAND & YAFFS
Date: Mon, 18 May 2009 09:39:00 -0000 [thread overview]
Message-ID: <4A112CC3.1040001@ecoscentric.com> (raw)
In-Reply-To: <20090516095007.GC31991@ma.tech.ascom.ch>
Andrew Lunn wrote:
> On Fri, May 15, 2009 at 12:18:49PM +0200, Simon Kallweit wrote:
>> Andrew Lunn wrote:
>>> Hi Folks
> [...]
>>> There is a possibility of it happening again soon
>>> as well. eCosCentric have a more modern lwIP port in there tree than
>>> the current in anoncvs. I understand they have optimized it for small
>>> platform and made it more stable. There is the current effort going on
>>> to update the anoncvs lwip code. When this reaches maturity, which
>>> looks like will happen soon, are eCosCentric going to pull out there
>>> trump card again and contribute there lwip port?
>> Well well, I almost saw that coming :/
>
> Would eCosCentric like to make a comment regarding this subject?
We have no plans to contribute our lwIP work. Developing the eCos public
version based on the very latest sources seems the appropriate way to go
long term.
Paul.
next prev parent reply other threads:[~2009-05-18 9:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-13 13:59 Ross Younger
2009-05-13 14:22 ` Simon Kallweit
2009-05-13 16:28 ` Sergei Gavrikov
2009-05-13 19:03 ` John Dallaway
2009-05-15 16:50 ` Ross Younger
2009-05-16 10:43 ` Andrew Lunn
2009-05-16 12:50 ` Ross Younger
2009-05-18 7:13 ` Andrew Lunn
2009-05-18 10:42 ` Rutger Hofman
2009-06-02 18:18 ` John Dallaway
2009-06-03 6:55 ` Andrew Lunn
2009-05-14 18:41 ` Rutger Hofman
2009-05-15 9:48 ` John Dallaway
2009-05-15 9:52 ` Andrew Lunn
2009-05-15 10:18 ` Simon Kallweit
2009-05-16 9:50 ` Andrew Lunn
2009-05-18 9:39 ` Paul Beskeen [this message]
2009-05-18 9:55 ` Simon Kallweit
2009-05-15 16:19 ` Paul Beskeen
2009-05-15 6:44 cetoni GmbH - Uwe Kindler
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=4A112CC3.1040001@ecoscentric.com \
--to=paulb@ecoscentric.com \
--cc=andrew.lunn@ascom.ch \
--cc=ecos-maintainers@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).