On Tue, Apr 27, 2021 at 05:28:46PM +0200, Miroslav Lichvar wrote: > An advantage of having multiple independent clients is that you can > better detect failures in synchronization and avoid corrupting the > other clocks.
Right. You can query the ptp4l instances (for example via pmc) and then pick the one to use (for CLOCK_REALTIME or whatever) based on the reported PARENT_DATA_SET. > The specification defines an ordinary clock as "A PTP Instance that > has a single PTP Port in its domain and maintains the timescale used > in the domain." > > If you run ptp4l with multiple specified interfaces, it cannot be an > ordinary clock. The boundary_clock_jbod and clientOnly options don't > matter here. +1 > I read the original patch+report again and it's not clear to me why > you need the port to be in the passive state. > > I tried --boundary_clock_jbod=1 --clientOnly=1 with two interfaces and > it seems to be switching them between the LISTENING and > UNCALIBRATED/SLAVE states as expected. Yeah, that is what I saw. Thanks, Richard _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
