On Mon, Mar 27, 2017 at 10:45:16AM +0200, Burkhard Ilsen wrote: > On Thu, Sep 15, 2016 at 08:55:34PM +0000, Richard Cochran wrote: > > So I do want to have TC/TAB in linuxptp for version 2.0. > > According to 802.1 AS all message timestamps shall be based on a free running > clock (LocalClock) in order to minimize the errors resulting from a varying > clock frequency. > Also phase discontinuities in the pdelay_resp(fup) messages are avoided this > way. > So the SlaveClock controlled by the servo is different from the hardware > clock taking the timestamps. > An implementation would require to translate hardware timestamps into the > SlaveClock epoch to compute the master offset correctly. > > I was not able to find this behavior implemented in linuxptp. Did I miss > something, or was this already issued?
You are mistaken. The master offset is irrelevant for TC operation. The TC is supposed to syntonize only. Thanks, Richard ------------------------------------------------------------------------------ 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
