On Mon, Jun 14, 2021 at 12:03:45PM +0000, Miklas, Marcin via Linuxptp-devel 
wrote:

> gPTP requires that PTP_TIMESCALE flag is set in messages. I noticed that
> PDelayReq, PDelayResp, PDelayRespFollowUp, Sync, FollowUp and Signaling all 
> have
> that flag set to 0. One of the bridges just ignores communication with ptp4l
> because of that.
> 
> The fault is on both sides, because gPTP specification says that PTP_TIMESCALE
> should be set to 1 and ignored on reception.

No, the fault is not on both sides.

> Since fixing linuxptp is easier I created a patch which should fix that 
> problem.

Adding a hack into linuxptp is easier than fixing the actual problem
in the other implementation, but that is a poor excuse.

> We can see that ptp4l slave is requesting gPTP master to use master's initial
> sync interval.  This might be different than slave's initial sync interval. If
> this is a case the signallings will be send over and over again.

No, in a correctly configured gPTP network, all of the nodes have the
same settings.

> Slave's own
> initalLogSyncInterval should be used here.
> 
> Current version is causing other problems with OpenAvnu's daemon_cl.

So fix daemon_cl.

NAK to both of these patches.

Thanks,
Richard


_______________________________________________
Linuxptp-devel mailing list
Linuxptp-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-devel

Reply via email to