lwip-devel
[Top][All Lists]
Advanced

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

[lwip-devel] [task #6683] Document lwIPs thread safety requirements


From: Jonathan Larmour
Subject: [lwip-devel] [task #6683] Document lwIPs thread safety requirements
Date: Fri, 20 Jul 2007 15:33:30 +0000
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.12) Gecko/20070530 Fedora/1.5.0.12-1.fc5 Firefox/1.5.0.12

Follow-up Comment #17, task #6683 (project lwip):

This may not be as helpful as it initially sounds, but I've written some
documentation for lwIP for the commercial version of eCos I am involved with
(called eCosPro). Much of it is derived (with acknowledgements, fear not)
from one of Adam Dunkel's documents; but updated to reflect the current
status.

Unfortunately it's not so helpful because:
- The Powers That Be restrict distribution on this ("Distribution of the work
or derivative of the work in any form is prohibited unless prior permission
obtained from the copyright holder.") as per
http://www.ecoscentric.com/ecospro/doc/html/ecospro-ref/ecospro-ref.html

- it's slanted specifically towards the eCosPro port, which is even different
from the eCos port, and has several patches (some of them contributed back
though) relative to the lwIP it was originally branched from (1.1.1).

Nevertheless, there would be no problem linking to it. However I won't be
offended if you don't want to, given the above drawbacks.

The direct link is:
http://www.ecoscentric.com/ecospro/doc/html/ecospro-ref/lwip.html

(In case you're wondering, the reason for the restrictions is so that we can
recoup the investment made in the first place - once that is done, we would
hopefully be able to relax things).


    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/task/?6683>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/





reply via email to

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