Changes between Version 3 and Version 4 of Packages/LWIP

Timestamp:

07/14/10 00:50:56 (14 years ago)

Author:

JoelSherrill

Comment:

Reverted edits by JenniferHouston? (Talk?) to last revision by JoelSherrill?

Packages/LWIP

@@ -2 +2 @@
 
 
-Travel writing jobs are few and far between. Getting into this field is hard to do and requires a lot of training and experience. But, there are many benefits to them. There are many individuals who would love to get employment opportunities in this field. And, because the world is faster and faster becoming accessible to more people, increasing employment availability can be found for travel jobs as well. But, how does a person get in and how do they do their job?Travel [http://www.freelancercareers.com/ writing jobs] belong mainly to freelance authors, travelling far and wide. They learn about the amusements, the attractions, and the little secrets of the towns, cities, and countries they visit. Then, they provide this knowledge to the general public in the form of articles, books, or even transcriptions. It is amazing that many people go from location to location by simply learning about different areas and using this knowledge to write. But, this work is far from easy. It may be costly to afford to do this type of traveling. It often does not pan out as a worthwhile adventure anyway. It is often difficult to find publishers or employment vacancies in this area as well.
+
+[[TOC(Packages/LWIP, depth=2)]]
+
+
+''Status:''' No active volunteers.
+
+Current Port: ftp://ftp.rtems.org/pub/rtems/people/joel/rtems-lwip/
+
+Update the RTEMS port of LWIP.  Provide reproducible test cases so we can be sure it stays in working condition.
+
+A goal of this effort is to be able to use the standard TCP/IP NIC drivers already in RTEMS.  If this is feasible, then a user could switch between the full-featured BSD TCP/IP stack in RTEMS or the LWIP stack to save memory at the expense of reduced functionality.
+
+The work would have to do :
+1 start with current LWIP source
+2 update the port for current RTEMS and current LWIP
+3 make the port portable across CPU architectures and BSPs (This is usually not as hard as it sounds.)
+4 Provide documentation and examples that run on at least
+qemu so others can provide feedback.
+5 Ideally use the standard BSD NIC drivers if at all technically possible so when you write a driver for one TCP/IP stack, you automatically get it for both stacks in RTEMS.