On Thu, Jun 07, 2018 at 03:43:59PM -0700, Cliff Spradlin via Linuxptp-devel wrote: > If ptp4l is running as a boundary clock, and multiple master ports > share a hardware clock that is different than the master's hardware
This should be "slave's hardware clock", right? > This patch prevents this problem by introducing a new deduplicated > destination clock list to phc2sys. Each time phc2sys reconfigures, > the destination clock list is re-populated. In the synchronization > loop, phc2sys will only use the clocks in this list. The fix makes sense to me, but it seems to break the manual mode (no -a option). It just sits there doing nothing. # ./phc2sys -s eth0 -O 0 -m phc2sys[1914653.180]: reconfiguring after port state change phc2sys[1914653.180]: selecting CLOCK_REALTIME for synchronization phc2sys[1914653.180]: selecting eth0 as the master clock Also, could we avoid printing these messages in the manual mode? -- Miroslav Lichvar ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Linuxptp-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
