public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: John Dallaway <john@dallaway.org.uk>
To: Simon Kallweit <simon.kallweit@intefo.ch>
Cc: ecos-devel@ecos.sourceware.org
Subject: Re: lwIP port status
Date: Tue, 18 Aug 2009 16:59:00 -0000	[thread overview]
Message-ID: <4A8ADDED.5010400@dallaway.org.uk> (raw)
In-Reply-To: <4A66F713.5030700@intefo.ch>

Hi Simon

Simon Kallweit wrote:

> lwip is close to the 1.3.1 release, and I think this will be the time
> to get the new port into the eCos repository, so any testing is highly
> appreciated.

lwIP 1.3.1 was finally released today.

In view of the known issues with the older eCos lwIP 1.1.1 port and the
many fixes to the master lwIP sources over the intervening years, I'm
keen to get this committed to eCos CVS as soon as possible.

Having reviewed the lwIP ChangeLog, I think it makes sense to simply
replace the older lwIP port in the eCos CVS trunk (tagging the
repository before the commit). There are known issues with lwIP PPP
which need to be addressed upstream. In the meantime, eCos users wishing
to work with lwIP PPP should be better off hacking on the lwIP 1.3.1
stack where necessary rather than using the older port.

What is the status of your testing of your lwIP 1.3.x port now? Are you
comfortable that it is stable under heavy CPU and network loads?

John Dallaway

  reply	other threads:[~2009-08-18 16:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-18 14:41 Simon Kallweit
2009-07-22 10:34 ` MaxiD
2009-07-22 11:22   ` Simon Kallweit
2009-08-18 16:59     ` John Dallaway [this message]
2009-08-18 17:33       ` Simon Kallweit
2009-08-19  7:11         ` John Dallaway
2009-08-19  9:21           ` Sergei Gavrikov
2009-08-19 12:11             ` Simon Kallweit
2009-08-19 12:10           ` Simon Kallweit

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=4A8ADDED.5010400@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).