Thank you Richard for your help.
> So we don't actually support TC or TAB. Those patches were only a
rudimentary proof of concept. Did you see the TODO list?
Yes, I saw it and I am looking forward to 2.0.
Until then I stick with an endpoint only implementation. In fact the
differentiation of LocalClock and ClockSlave makes sense for endpoints too.
My task is to prototype an industrial TSN node. My hardware supports taking
two timestamps (from two different hardware clocks) for each message.
> 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.
I already implemented a third option: I messed with the linuxptp code so
that timestamps relative to LocalClock are passed into delay measurement
and timestamps relative to ClockSlave are passed into the servo. It works
very well.
I stumbled upon some minor issues that I will address in other threads.
Best Regards,
Burkhard
------------------------------------------------------------------------------
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
