[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE : [lwip-users] Problem with lwip_close in TCP

From: Christiaan Simons
Subject: RE : [lwip-users] Problem with lwip_close in TCP
Date: Wed, 14 Jun 2006 09:50:43 +0200


> In a general way, how to contrib to Lwip? The only document I see
> was about coding conventions.

The doc/contrib.txt does give some hints on how to proceed,
but it doesn't give the gory details. (It's assumed you have this

Contributing as non-member can be done by submitting a
patch file to http://savannah.nongnu.org/patch/?group=lwip

To create such a patch file use this command :

diff -urN lwip_x_y_z.orig lwip-x_y_z.new > your_fantastic.patch

where lwip-x_y_z.orig is the unchanged lwip release directory tree
(our sources!) and lwip-x_y_z.new has your local changes.

If you don't have access to a unix box for the 'diff' command you
could use the Cygwin tools or if you use TortoiseCVS you could use
the command "Make Patch" on your local changes.

Note patches should only tackle one subject so we can easily commit
these without we having to detangle too much stuff we dislike.

> I have integrate to lwip1.1.1 the steve reynolds code for IGMP with
> several corrections. I also add a sock_init() function to initialize
> sockets.c semaphores like other _init() functions. And I add a DNS
> client to lwip to provide "BSD like" gethostby... functions.

I was reluctant to integrate IGMP stuff since it is an invasive change,
and changes were possbily not in the 'right' places.

Sorry, we're a bit laggin behind on fixing and cleaning stuff up.

> I'm also interested about a SNMP agent for my product. Do you intend
> to add it to the stack?

I can't tell this yet, I'll need approval from my boss first.
Keep an open eye on this list.


Christiaan Simons

Hardware Designer
Axon Digital Design


reply via email to

[Prev in Thread] Current Thread [Next in Thread]