Hello Miroslav and Richard, Thank you very much for your discussion and clarifications.
We are trying to make one of our devices PTP compatible so we are thinking in using your linuxptp. The problem is that we need the telecom profile (ITU G.8265.1) and that specific profile uses unicast traffic. That was the reason why I asked about the unicast traffic. Regards, Emilio. El 17/02/17 a las 11:27, Miroslav Lichvar escribió: > On Fri, Feb 17, 2017 at 11:12:37AM +0100, Richard Cochran wrote: >> On Fri, Feb 17, 2017 at 10:03:35AM +0000, Urs Ritzmann wrote: >>> But I was still concerned that we could get such a transient for any >>> reason. Perhaps NTP was not yet ready to tune the system clock which >>> invalidates that initial measurement. >> But ntpd avoids sudden system clock adjustments, doesn't it? > Normally it does, but on start, if the offset is smaller than 128ms, it > doesn't step the clock and depending on the time constant it may > take hours to correct and stabilize. With the lastest ntpd version > (4.2.8), it's faster. Running ntpdate before ntpd may help. > ------------------------------------------------------------------------------ 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
