> -----Original Message----- > From: Petr Kulhavy [mailto:br...@jikos.cz] > Sent: Monday, January 29, 2018 4:27 AM > To: linuxptp-devel@lists.sourceforge.net > Subject: [Linuxptp-devel] Transport specific for phc2sys > > Hi, > > if ptp4l uses other transport specific number than 0, it seems phc2sys > cannot be used to synchronize the system clock. > Phc2sys passes constant 0 as transport specific to pmc_create(). > This results to infinite "Waiting for ptp4l..." > > What about adding a config option to set the transport specific, same as > pmc has? > > Thanks > Petr
Could phc2sys determine this information automatically? or does it need to know this prior to ptp4l being enabled? Could we instead have the automatic mode do some sort of scanning to find it out? Thanks, Jake ------------------------------------------------------------------------------ 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 Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
