On Mon, Sep 05, 2022 at 05:21:32PM +0200, Miroslav Lichvar wrote: > 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.
It could be either Announce on UDS (enabled via option) or a second UDS port just for Announce/bmca, which ever one makes most sense. > In the jbod mode there are multiple hardware clocks. I don't see how > would phc2sys work only with announce messages. depending on phc2sys "port" role: slave -> synchronize clock_realtime to PHC of master port master -> synchronize all PHC master ports to clock_realtime Hm? (maybe simpler for phc2sys to react to the UDS port role with inverted logic) Thanks, Richard _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
