Am 2018-08-18 01:39, schrieb Richard Cochran:
On Sat, Aug 18, 2018 at 01:08:27AM +0200, Michael Walle wrote:
calnex and ixia (and i guess spirent too) support reverse sync to
measure the clock accuracy.
Those two have showed zero interest in helping linuxptp. Why should
we help them?
Think
On Fri, Aug 17, 2018 at 07:39:15PM -0400, Richard Cochran wrote:
> If this reverse sync thingy makes it into 1558 v2.1 or the next
> 802.1-AS revision, then we can consider supporting it.
BTW, is this reverse sync present in the current drafts for either
standard?
I don't recall seeing it, but if
On Sat, Aug 18, 2018 at 01:08:27AM +0200, Michael Walle wrote:
> calnex and ixia (and i guess spirent too) support reverse sync to measure the
> clock accuracy.
Those two have showed zero interest in helping linuxptp. Why should
we help them?
If this reverse sync thingy makes it into 1558 v2.1
Am 17. August 2018 18:07:30 MESZ schrieb Richard Cochran
:
>On Tue, Aug 14, 2018 at 02:56:44PM +0200, Michael Walle wrote:
>> AVnu specifies a measurement method to remotely measure the clock
>> quality. Basically, this method sends Sync and/or Follow-up messages
>on
>> a slave towards the master,
On Tue, Aug 14, 2018 at 02:56:44PM +0200, Michael Walle wrote:
> AVnu specifies a measurement method to remotely measure the clock
> quality. Basically, this method sends Sync and/or Follow-up messages on
> a slave towards the master, which can capture them and measure the
> quality.
We already ha
AVnu specifies a measurement method to remotely measure the clock
quality. Basically, this method sends Sync and/or Follow-up messages on
a slave towards the master, which can capture them and measure the
quality.
The AVnu specification [1] introduces three parameters:
- reverseSyncEnabled
- rev
