Hi Vijay and Kinsey, I monitor from distance LwIP for RTEMS progress and I am happy for that and when the code settles and I find a time, I try to test it with TMS570. But I have notices next moves
On Thursday 14 of April 2022 22:08:00 Vijay Kumar Banerjee wrote: > rename {lwip => uLan}/ports/os/lwipopts.h (100%) > > > rename {lwip => uLan}/ports/os/rtems/arch/cc.h (100%) > > rename {lwip => uLan}/ports/os/rtems/arch/perf.h (100%) > > rename {lwip => uLan}/ports/os/rtems/arch/sys_arch.c (100%) > > rename {lwip => uLan}/ports/os/rtems/arch/sys_arch.h (100%) please do not use uLAN for directory name inside LwIP. uLAN is our RS-485 communication protocol project and it includes sysless (bare hardware integration layer) as well as others for RTEMS, NuttX, GNU/Linux. And LwIP is used as subproject inside our larger projects. Yes, project is used as base for more our project even unrelated to RS-485 but that is historical relict and should not propagate into RTEMS. But there is no reason to keep uLAN in the name. These parts which I have written myself or has been writtent by Roman Bartosinski under my company (PiKRON) and colleague Alvat.cz funding acan be relicensed under any RTEMS compatible preferred license. Only me and Roman needs to agree on that and I do not see that as a problem. So do not put there uLAN name. This RTEMS specific integration should stay in some RTEMS specific LwIP subdirectory or can be even included into RTEMS mainline. But please, do not add there uLAN name nor OMK (our makesystem abbreviation). Best wishes, Pavel -- Pavel Pisa phone: +420 603531357 e-mail: p...@cmp.felk.cvut.cz Department of Control Engineering FEE CVUT Karlovo namesti 13, 121 35, Prague 2 university: http://control.fel.cvut.cz/ company: https://www.pikron.com/ personal: http://cmp.felk.cvut.cz/~pisa projects: https://www.openhub.net/accounts/ppisa CAN related:http://canbus.pages.fel.cvut.cz/ Open Technologies Research Education and Exchange Services https://gitlab.fel.cvut.cz/otrees/org/-/wikis/home _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel