Changes between Version 4 and Version 5 of Packages/LWIP


Ignore:
Timestamp:
Mar 7, 2012, 5:47:46 AM (7 years ago)
Author:
Gedare
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Packages/LWIP

    v4 v5  
    1010Current Port: ftp://ftp.rtems.org/pub/rtems/people/joel/rtems-lwip/
    1111
    12 Update the RTEMS port of LWIP.  Provide reproducible test cases so we can be sure it stays in working condition.
     12Update the RTEMS port of LWIP.  Provide reproducible test cases so we can be sure it stays in working condition. See discussion on [wiki:Https://www.rtems.org/pr1712 PR1712]
    1313
    1414A 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.
    1515
    1616The work would have to do :
    17 1 start with current LWIP source
    18 2 update the port for current RTEMS and current LWIP
    19 3 make the port portable across CPU architectures and BSPs (This is usually not as hard as it sounds.)
    20 4 Provide documentation and examples that run on at least
    21 qemu so others can provide feedback.
    22 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.
     17# start with current LWIP source
     18# update the port for current RTEMS and current LWIP
     19# make the port portable across CPU architectures and BSPs (This is usually not as hard as it sounds.)
     20# Provide documentation and examples that run on at least qemu so others can provide feedback.
     21# 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.