As I highlighted earlier, I, along with other users of ptp4l, don't feel the linuxptp project is the right place for the submission of the ITU-T ESMC Protocol (which is based on recommendations G.8274 & G.781). There are no dependencies on ESMC with the 1588 protocol or the Linux PHC, nor is the linuxptp maintainer wanting to be a bottleneck for contributions to the ESMC protocol (as highlighted below from Richard).
>My main concern is the fact that my time is limited to work on >linuxptp, and >I already have a back log of patches. If synce will have >rapid development, >new features, etc, then I don't want to be the >bottleneck. To address this concern, Renesas has submitted our open implementation of the ESMC protocol to github, also under the same name: https://github.com/renesas/synce4l. This is an open project under GPLv2, and we welcome contributions to it. The implementation not only addresses the ESMC protocol per G.8264, but also includes some additional features from G.781. We realize there will be a need to provide QL and other information from synce4l to ptp4l, per applicable ITU-T 1588 Profiles, and look forward to collaborating with the linuxptp community to produce these interfaces. We will also be working with the Network Time Foundation to see if they would be willing to oversee synce4l project like the other Linux projects they already manage, including linuxptp. We have also already shared synce4l project with other MAC/PHY/SoC vendors looking for an ESMC protocol solution. Regards, Greg Greg Armstrong Principal System Architect, Timing Products Division Renesas Electronics Canada Limited Mobile: 1-613-218-9373 -----Original Message----- From: Miroslav Lichvar <mlich...@redhat.com> Sent: Thursday, June 2, 2022 6:23 AM To: Erez <erezge...@gmail.com> Cc: Greg Armstrong <greg.armstrong...@renesas.com>; piotr.kwapulin...@intel.com; andrzej.saw...@intel.com; linuxptp-devel@lists.sourceforge.net; anatolii.gerasyme...@intel.com Subject: Re: [Linuxptp-devel] [PATCH 00/11] synce4l: add software for Synchronous Ethernet On Wed, Jun 01, 2022 at 05:37:10PM +0200, Erez wrote: > I do hope my project > https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsf.net%2Fp%2Flibptpmgmt%2F&data=05%7C01%7Cgreg.armstrong.uw%40renesas.com%7C08ec39f69e6347d0a63d08da4481ecaa%7C53d82571da1947e49cb4625a166a4a2a%7C0%7C0%7C637897622057580969%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Ud1Te2%2BA87xSSj9z1qkhgPyQ4MoLr5tHmUvB58XygW0%3D&reserved=0, > does help to fill this gap and helps with reducing the overhead from this > project. > phc2sys can be implemented with libptpmgmt. > I already cloned pmc with libptpmgmt. > > Maybe it is time that this project focuses on ptp4l and let other > applications have their own projects. phc2sys shares quite a lot of code with ptp4l, it's not just the PTP management support. It it was a separate project, it would need to duplicate the code, or linuxptp would need to provide and maintain a library. If some components had a different maintainer, it doesn't mean it has to be a separate project or repository. -- Miroslav Lichvar _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
