On Mon, Mar 27, 2017 at 12:32:46PM +0200, Burkhard Ilsen wrote: > My use case is a bridged end-station, i.e. a time-aware bridge with an > application that needs to be synchronized.
So we don't actually support TC or TAB. Those patches were only a rudimentary proof of concept. Did you see the TODO list? > The AS model of operation allows every time-aware system (including TAB) to > include a ClockSlave and provide an application interface to a ClockTarget. If you are talking about 802.1AS-2011 Clause 9, then I recommend just ignoring it. It is not one of the more brilliant examples of standards writing. In linuxptp, applications can find out everything they need to know via the management interface. In particular, the TIME_STATUS_NP TLV is designed for use with gPTP and the free_running option. > Syntonization is done by multiplying the residence time with the rate ratio, > no servo needed, right? No, syntonization means choosing a master and calculating the rate ratio. > So the servo should be free for synchronizing the ClockSlave but this > requires the offset. > Would this be possible with linuxptp? > Any advice is appreciated. You have two options: 1. Use TIME_STATUS_NP and implement the servo in the application. 2. Adjust the TC clock. Depending on your environment, this may be acceptable. Even though 802.1AS-2011 says not to, 1588 allows it. HTH, 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
