On Thu, Apr 22, 2021 at 09:04:28AM +0000, Amar Subramanyam via Linuxptp-devel wrote: > >But you haven't even identified a problem. clientOnly and > >boundary_clock_jbod work just fine together: > > 1. Using boundary_clock_jbod has few issues which weren’t mentioned > earlier(see mail trail for the issues). > > Also boundary_clock_jbod might not be right term to be used for Ordinary > Clock Client/Slave/Sub-ordinate modes. > > Boundary Clock and Ordinary are two different clocks.
I don't have a solution for the described issue. I think it's generally better to run multiple ptp4l instances. Just a comment about terminology. Per IEEE1588 ordinary clock has a single port and boundary clock has multiple ports. You seem to be talking about a clock with multiple ports. "jbod" is an option to assume all ports belong to a single clock. -- Miroslav Lichvar _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
