public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: Simon Kallweit <simon.kallweit@intefo.ch>
To: John Dallaway <john@dallaway.org.uk>
Cc: ganesh kr <krganesh01@gmail.com>,
	  eCos developers <ecos-devel@ecos.sourceware.org>
Subject: Re: lwip 1.3.2 port
Date: Fri, 22 Jan 2010 14:43:00 -0000	[thread overview]
Message-ID: <4B59B98F.5010106@intefo.ch> (raw)
In-Reply-To: <4B59A8C1.5040903@dallaway.org.uk>

John Dallaway wrote:
> Hi Simon
> 
> Simon Kallweit wrote:
> 
>> Hi John,
>> Hi Ganesh
>>
>> Nice to hear that you are using the lwip stack and it is working fine
>> for you. Currently, I hold the lwip code in my own git repo, shared with
>> other changes I have done to eCos. The plan was to get my current lwip
>> code into the CVS. John, I think it's about time to get this done. I can
>> do one latest merge with the lwip 1.3.2 codebase and then we should be
>> ready.
>>
>> I still have some local changes concerning ppp in my repo (which are
>> absolutely necessary in my current project). But I think we should keep
>> these changes in for a while. It seems like some work is done in the
>> official lwip repo, concerning ppp. But these changes will only be
>> available in future 1.4.x releases. The current stable release is 1.3.2,
>> and will be for a little while. When we get to a stable 1.4.x release,
>> it may be a good time to get back to the lwip repositories ppp code. In
>> the meanwhile, I'll keep track of what's happening in the official repo
>> and try to incorporate my changes into the official repo (support for
>> ppp in a single-threaded lwip environment).
>>
>> What do you think?
> 
> Sounds good to me. Please let me know when your final lwIP 1.3.2 tarball
> is available for download/review.

Ok, I merged the 1.3.2 stable code and did a few quick tests (the 
changes are not huge). The tarball is at 
http://download.westlicht.ch/lwip-20100122.tar.gz

Simon

  reply	other threads:[~2010-01-22 14:43 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           ` Simon Kallweit
2010-01-22 13:31             ` John Dallaway
2010-01-22 14:43               ` Simon Kallweit [this message]
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                             ` lwIP 1.4.0 port planning [ was Re: lwip 1.3.2 port ] John Dallaway
2011-06-07 20:28                               ` 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=4B59B98F.5010106@intefo.ch \
    --to=simon.kallweit@intefo.ch \
    --cc=ecos-devel@ecos.sourceware.org \
    --cc=john@dallaway.org.uk \
    --cc=krganesh01@gmail.com \
    /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).