public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: John Dallaway <john@dallaway.org.uk>
To: John Eigelaar <john@kses.net>, Simon Kallweit <simon.kallweit@intefo.ch>
Cc: eCos development list <ecos-devel@ecos.sourceware.org>
Subject: Re: lwIP
Date: Sat, 04 Apr 2009 14:54:00 -0000	[thread overview]
Message-ID: <49D77480.7040408@dallaway.org.uk> (raw)
In-Reply-To: <1227539519.4641.40.camel@janet>

Hi John and Simon

John Eigelaar wrote:

> On Fri, 2008-11-21 at 14:49 -0500, Frank Pagliughi wrote:
>> Simon Kallweit wrote:
>>> Simon Kallweit wrote:
>>>> Frank J. Beckmann wrote:
>>>>> Hello,
>>>>>
>>>>> are there plans for updating eCos' lwIP port to a more recent version?
>>> I just had a quick look of the lwIP in the current ECOS version. It 
>>> differs just very slightly from the actual lwIP 1.1.1 release, not 
>>> many changes. I guess an update to a more recent lwIP version should 
>>> be pretty simple and straight forward. I'll start working on it in 
>>> around a week, have to get my GSM modem working first :)
>>>
> I have been trying on and off tp port lwip 1.3.0 to ecos. The current
> version has a serious memory leak when under fire and also does not
> honor the backlog parameter for lwip_listen and lwip_accept mechanisms.
> 
> In 1.3.0 the init part of the lwIP source has been greatly improved and
> now works well to initialise the lwIP stack but is of course now
> completely incompatible with the existing eCos port. The sys_arch API
> has been update as well to counetr the aforementioned memory leaks.
> 
> I am also not sure what to do really with the IPv6 and IPv4 config
> options for the lwIP stack.
> 
> I have compiled the test cases with the new 1.3.0 source but I  still
> can not get any of them to run on the Linux synth target. Some of it is
> actualy me learning the synth target as I go along as well as me not
> really having any time to spend on this other than time set aside out of
> curiosity.

I am keen to see lwIP updated in the eCos repository and can offer help
with the CDL if necessary.

It looks like good progress has been made with lwIP 1.3.0 on eCos
already. Could you drop a note to this list with the current status of
your work please and we can plan accordingly?

Given the changes in the lwIP initialisation code, can anyone comment on
the likely effort to port an eCos application based on the existing eCos
lwIP stack to lwIP 1.3.0?

lwIP is a good fit for eCos and I can see the use of this stack
dominating in the future. With this in mind, it would be great to
support as many features of the stack as possible (including IPv6).

John Dallaway

  reply	other threads:[~2009-04-04 14:54 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         ` John Dallaway [this message]
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   ` lwIP Jonathan Larmour
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=49D77480.7040408@dallaway.org.uk \
    --to=john@dallaway.org.uk \
    --cc=ecos-devel@ecos.sourceware.org \
    --cc=john@kses.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).