Changes between Version 20 and Version 21 of Packages/LWIP


Ignore:
Timestamp:
07/18/22 15:34:21 (20 months ago)
Author:
Kinsey Moore
Comment:

Update status of lwip for ZynqMP and other merges to "main"

Legend:

Unmodified
Added
Removed
Modified
  • Packages/LWIP

    v20 v21  
    77
    88''Status:''' rtems-lwip is currently under development.
    9 Active volunteers: Vijay Kumar Banerjee.
     9Active volunteers: Vijay Kumar Banerjee, Kinsey Moore
    1010
    11 The current development branch is the 'devel' branch at: https://git.rtems.org/vijay/rtems-lwip.git.
     11All in-development work has been merged into the "main" branch at: https://git.rtems.org/vijay/rtems-lwip.git.
    1212
    1313Current status of rtems-lwip:
    1414
    1515* Tested with telnetd01 test on Beaglebone Black.
     16* Tested with ZynqMP BSP on ZCU102 and QEMU
    1617* TMS570 drivers added, but not tested yet.
    1718* Work-in-Progress: STM32 support is being added and it'll be pushed to the devel branch once tested with hardware.
    1819
    19 
    20 Project mainline/upstream repository: git://git.savannah.nongnu.org/lwip.git
     20Source origin repositories are documented in the ORIGIN.* files in the rtems-lwip repository.
    2121
    2222RTEMS Source Builder configuration files lwip-1-1.cfg and lwip-1.cfg are located in next RSB locations
     
    2727
    2828Update the RTEMS port of LWIP.  Provide reproducible test cases so we can be sure it stays in working condition. See discussion on #1712.
    29 
    30 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.
    31 
    32 The work would have to do :
    33 1. start with current LWIP source
    34 1. update the port for [http://git.rtems.org/rtems/snapshot/rtems-4.10.2.tar.bz2 current RTEMS] and [http://download.savannah.gnu.org/releases/lwip/ current LWIP]
    35 1. make the port portable across CPU architectures and BSPs (This is usually not as hard as it sounds.)
    36 1. Provide documentation and examples that run on at least [http://www.rtems.org/wiki/index.php/QEMU qemu] so others can provide feedback.
    37 1. 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.
    38 
    39 Some other LwIP porting attempt with TMS570, LCP17xx drivers with RTEMS, POSIX and systemless adaptation layers is available from uLAN project repository.
    40 
    41 https://sourceforge.net/p/ulan/lwip-omk
    42 
    43 LwIP arch support for RTEMS in lwip-omk port
    44 
    45 https://sourceforge.net/p/ulan/lwip-omk/ci/master/tree/ports/os/rtems/
    46 
    47 This project build is based on OMK system but for use in RTEMS it should be changed to something matching RTEMS standard build system (even that configurability and multiple target systems support is lost but drivers selection should be kept somehow. One option is to move actual drivers to RTEMS BSP directories but sometimes they can be reused between more architectures so may it be left them in LwIP support tree is better option.
    48 
    49 Other RTEMS LwIP port by Ragunath for Beagle Bone board
    50 
    51 http://ragustechblog.blogspot.cz/2015/08/rtems-beaglebone-black-with-lwip.html
    52 
    53 git://github.com/ragunath3252/lwip-app.git
    54 
    55 git://github.com/ragunath3252/lwip-nodrv
    56 
    57 Old 2008 port: ftp://ftp.rtems.org/pub/rtems/people/joel/rtems-lwip/
    5829
    5930== LwIP Integration with RTEMS File Descriptors ==