On Mon, Sep 05, 2022 at 07:20:49AM -0700, Richard Cochran wrote: > I can imagine that allowing an Announce messages on the UDS port and > letting the UDS port participate in BMCA might make the whole system > easier to understand/configure.
I suspect I'd find it more confusing. UDS is intended for monitoring and management. It is not a port of the clock that can be used for synchronization. A hardware clock cannot timestamp UDS messages. In the jbod mode there are multiple hardware clocks. I don't see how would phc2sys work only with announce messages. > For this we would need: > > - proper BMCA logic in phc2sys and ts2phc Turning the system clock (phc2sys) and reference clock (ts2phc) into a virtual PTP clock? I like the idea of reusing PTP for synchronization to/from the system clock, and I think I already proposed it some time ago, but it would need ptp4l to be combined with phc2sys in order to create a true virtual network where timestamping of sync and delay_req messages can provide the same level of accuracy (i.e. sharing the timestamps from the SYS_OFFSET ioctl). -- Miroslav Lichvar _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
