Standalone repository for libnetworking stack
Vijay Kumar Banerjee
vijay at rtems.org
Thu Feb 25 17:49:42 UTC 2021
The stand-alone repository is very close to completion now and I could
use the networking01 test with the standalone repo and it successfully
runs on pc-qemu. The following are the links to the branches with the
final version of the commits and I would really appreciate a review
and suggestions on what else needs to be done (I'm not sending patches
as they're big and would hit the devel limit):
There are at least two things that need to be done:
1. Shift the tests like mghttpd01 that use the libnetworking stack, to
the standalone repo like networking01
2. There are still codes that use the #ifdef RTEMS_NETWORKING. What do
we want to do about those?
Apart from these two points above, do the commits and the standalone
repo look OK (close to mergeable)?
On Tue, Feb 9, 2021 at 5:47 PM Vijay Kumar Banerjee <vijay at rtems.org> wrote:
> On Tue, Feb 9, 2021 at 3:31 PM Chris Johns <chrisj at rtems.org> wrote:
> > On 6/2/21 10:17 am, Vijay Kumar Banerjee wrote:
> > > Hello Christian, Joel, Chris,
> > >
> > > On Fri, Feb 5, 2021 at 3:41 PM Chris Johns <chrisj at rtems.org> wrote:
> > >>
> > >> On 6/2/21 8:28 am, Joel Sherrill wrote:
> > >>> On Fri, Feb 5, 2021 at 2:54 PM Christian Mauderer <oss at c-mauderer.de
> > >>> <mailto:oss at c-mauderer.de>> wrote:
> > >>>
> > >>> Hello Vijay,
> > >>>
> > >>> On 05/02/2021 19:41, Vijay Kumar Banerjee wrote:
> > >>> > Hello,
> > >>> >
> > >>> > I'm currently working on separating the libnetworking stack into its
> > >>> > standalone repository that can be built separately with waf. The current
> > >>> > status of the project is that I have a working rtems-libnetworking
> > >>> > repository  that builds with waf (hasn't been tested with any test
> > >>> > cases yet). And In my fork of RTEMS I have separated the libnetworking
> > >>> > stack .
> > >>
> > >> If you have not already done so I suggest you create repos in your personal area
> > >> on dispatch.rtems.org and these will appear on the cgit page. It is a simple way
> > >> to get exposure to the work.
> > >>
> > > I do have some repos in my area in dispatch.rtems.org but for some
> > > reason they don't appear in git.rtems.org page that's why I pushed it
> > > in github. Am I possibly missing some step?
> > I have fixed the cgit viewing. I am sorry for the delay.
> > Your repos are there, valid and available. On dispatch.rtems.org in
> > /data/git/users a symlink needs to be set to your physical repo path under
> > /data/git. I have done this. The cgit server is configured to scan
> > /data/git/user so it does not pick some dormant but present repos.
> Thanks! It's now working and here's the rtems-net-legacy repo:
> Best regards,
> > Chris
More information about the devel