From: Simon Kallweit <simon.kallweit@intefo.ch>
To: John Dallaway <john@dallaway.org.uk>
Cc: ecos-devel@ecos.sourceware.org
Subject: Re: lwIP port status
Date: Wed, 19 Aug 2009 12:10:00 -0000 [thread overview]
Message-ID: <4A8BEBB1.1080504@intefo.ch> (raw)
In-Reply-To: <4A8BA58D.8020805@dallaway.org.uk>
John Dallaway wrote:
> Hi Simon and all
>
> Simon Kallweit wrote:
>
>> John Dallaway schrieb:
>>
>>> 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.
>> I think this is the way to go. There is already some hacking on PPP in
>> my port, which could lead to some confusion, as it is not identical to
>> the lwIP codebase. Also it does only work in a polled environment like
>> mine, so it might not be much use of the broad community. I don't know
>> how we should proceed with this?
>
> Perhaps it would be preferable to publish your PPP-related changes as a
> patch for the time being and keep the CVS sources as close to the master
> lwIP code as possible.
That sounds like a good idea. I'll look into it.
I'll do the merge with the newest lwip sources tomorrow and release the
package.
Simon
prev parent reply other threads:[~2009-08-19 12:10 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
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 [this message]
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=4A8BEBB1.1080504@intefo.ch \
--to=simon.kallweit@intefo.ch \
--cc=ecos-devel@ecos.sourceware.org \
--cc=john@dallaway.org.uk \
/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).