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: Mon, 06 Apr 2009 16:46:00 -0000	[thread overview]
Message-ID: <49DA31CE.6000509@dallaway.org.uk> (raw)
In-Reply-To: <1239014653.28428.4.camel@janet>

Hi John and Simon

On Mon, 2009-04-06 at 11:44 +0200, Simon Kallweit wrote:

> Anyone interested in my code may have a look at 
> http://git.inthemill.ch/?p=ecos.git;a=summary
>
> I think it would be great to update the official lwip port in ecos and 
> I'm willing to help where I can.

and John Eigelaar replied:

> I will be more than willing to carry on from Simon's port in order to
> get the sequential part going, as he has made much better progress than
> I have. We almost exclusively use the stack in sequential mode on the
> AT91 SAM7 mcu, so test environments should not be a problem.
> 
> Maybe we can get this port in some time soon then.

This looks like an excellent opportunity to demonstrate the benefits of
our free open source development model.

In a perfect world, it would be great to see:

a) Support for all functionality of lwIP 1.3.0 (including ethernet, PPP,
   IPv4, IPv6, raw API, sequential API, BSD socket API)
b) Compatibility with eCos applications using the existing eCos lwIP
   1.1.1 package if possible (API and existing CDL option names
   preserved)
d) Absolutely minimal mangling of the lwIP sources (it should be easy to
   upgrade lwIP again in the future)
e) All lwIP configuration points accessible via CDL options
f) DocBook (.sgml) documentation which describes any eCos-specific
   aspects of the stack and otherwise points to generic lwIP
   documentation
g) Any fixes necessary in the lwIP sources contributed up to the master
   lwIP project for inclusion in the next generic release
h) eCos test cases for all functionality

Of the above, IPv6 is probably the least likely to get covered. Note
that IPv6 requires multicast support (CYGINT_IO_ETH_MULTICAST) in the
eCos ethernet driver. Is there anyone with an IPv6 network to hand who
could put some effort into the IPv6 side? Perhaps on i386 PC hardware
with the RTL8139 or i82559 ethernet drivers which already support
multicasting?

Perhaps the best way forward is for John Eigelaar to take Simon
Kallweit's package, work on the sequential API initially and post his
revised package for review and further work by others. Simon, is the
lwIP package in your repository ready for handoff?

Many thanks to both of you

John Dallaway

  reply	other threads:[~2009-04-06 16:46 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         ` lwIP John Dallaway
2009-04-06  9:44           ` lwIP Simon Kallweit
2009-04-06 10:44             ` lwIP John Eigelaar
2009-04-06 16:46               ` John Dallaway [this message]
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=49DA31CE.6000509@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).