EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  <20212022  2023  2024  Index 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  <20212022  2023  2024 
<== Date ==> <== Thread ==>

Subject: ANN: RTEMS libnetworking relocation
From: Vijay Kumar Banerjee via Core-talk <core-talk at aps.anl.gov>
To: core-talk at aps.anl.gov
Date: Mon, 1 Mar 2021 15:43:04 -0700
Hello all,

In RTEMS 6, there will be no cpukit/libnetworking in the RTEMS
repository and it will be moved to its own separate repository. There
are ongoing efforts in this direction and it is very close to
completion. What's remaining, is to collect feedback from the users of
the libnetworking stack.

The legacy repo, in its current state, has been tested with pc-qemu
and it can successfully run the legacy networking tests.

The following are the links to the repositories with the latest
version of changes:
RTEMS: https://git.rtems.org/vijay/rtems.git/log/?h=devel-no-libnet
Legacy Network: https://git.rtems.org/vijay/rtems-net-legacy.git/log/?h=main

The following BSP family in RTEMS has been used with the old legacy
networking stack:
Zynq, PC, Motorola Shared, Beatnik, mvme3100, mvme5500, gen68360,
uc5282, mvme 162/167

If anyone is maintaining/working with one (or more) of these BSPs,
please let me know if you're able to test the separate legacy-net
repository and if you have any feedback. If you're planning to test
it, please add your comments here so that we know someone is going to
do it and wait for your feedback. The changes will not be pushed right
away and we'll follow-up for your feedback.

What's next?

The legacy networking repository will stay at git.rtems.org for any
projects that are still using it. It is recommended that the new
projects use the libbsd networking stack which is more full-featured.
There is a strong possibility that we will add lwip next, but no
timeline has been decided for it yet. We plan to provide a performance
analysis of lwip and libbsd networking (and maybe legacy networking as
well)

Thank you for your patient reading. Any suggestion is welcome and I'm
more than happy to work with you to get it more thoroughly tested.

Best regards,
Vijay

Replies:
Re: ANN: RTEMS libnetworking relocation Vijay Kumar Banerjee via Core-talk
Re: ANN: RTEMS libnetworking relocation Michael Davidsaver via Core-talk

Navigate by Date:
Prev: epics-7.0 » linux32 - Build # 301 - Fixed! APS Jenkins via Core-talk
Next: Re: ANN: RTEMS libnetworking relocation Vijay Kumar Banerjee via Core-talk
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  <20212022  2023  2024 
Navigate by Thread:
Prev: [Bug 1881563] Re: Empty arrays have undefined behavior Andrew Johnson via Core-talk
Next: Re: ANN: RTEMS libnetworking relocation Vijay Kumar Banerjee via Core-talk
Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  <20212022  2023  2024 
ANJ, 03 Mar 2021 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·