>> 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
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
