Re: [lwip-devel] Cleanout of old ports

[Siva Velusamy]

Hi Kieran --

I work at Xilinx and am in the process of porting lwip-1.2.0 to the new Xilinx EMAC IP's. As much as I'd like to say I'll continue maintaining these new ports, I'm not sure if that'll hold if I have to change projects down the line. However, what I can provide within the next 3 to 4 months would be some of these:

- new port to Xilinx TEMAC and ethernetlite cores
- some sample applications we've been using internally including rxperf and txperf clients that are used with iperf (
http://dast.nlanr.net/Projects/Iperf/) for throughput measurements.
- some documentation on the steps I had to go through while porting to the Xilinx EMACs - hopefully this will be useful to anyone creating a new port
- some debugging/performance optimization hints

Unfortunately all of them will have a Xilinx bent to it, simply because that is the only platform in which I've used lwIP. Hopefully we could collaborate and make things more generic if need be.

In the meantime I'd like to thank all the developers for having creating a simple and useful stack.

-Siva
-- 
In the end, everything is a gag.
           Charlie Chaplin

On 6/14/07, Kieran Mansley <address@hidden> wrote:

A few months ago I suggested archiving any of the ports in the lwIP
contrib module that didn't have an active maintainer, and asked people
to step up as maintainers if they have an interest in support for a port
continuing.  It's not very surprising that no one stood up!

As a result, I've now archived all the ports except the example unix one
(which I'm happy to be the nominal maintainer, although I'm sure other
developers will also make modifications here when appropriate).  The
archived ones are still in CVS, but live in the ports/old directory.

This email has three purposes
  i) to let you know of this change;
ii) to ask if anyone would like to be a port maintainer and rescue a
port from the "old" subdirectory;
iii) to ask if there are any maintained ports held externally to the
contrib module (for example, I think the ecos port is maintained this
way).  It would be good to create a list of these.

Hopefully we should be getting some new actively maintained ports added
in the near future to fill some of the void that this change has left!

Finally, it would be nice to have a few more example apps in the contrib
module, but again I'm keen that any code we distribute is maintained to
keep up with the current lwIP release.  If anyone would like to
contribute an example app, and maintain it, please get in touch.

Kieran



_______________________________________________
lwip-devel mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/lwip-devel