Hi,
I noticed problem with signalling messages. When servo is unlocked the
following function is called:
port_tx_interval_request(p, SIGNAL_NO_CHANGE,
SIGNAL_SET_INITIAL,
SIGNAL_NO_CHANGE);
We can see that ptp
Hi,
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
Hi,
Updated patch is attached. The patch is created for v3.1 tag but it is applying
smoothly also to master branch.
Regards,
Marcin
From: Richard Cochran
Sent: 05 March 2021 3:27
To: Miklas, Marcin
Cc: linuxptp-users@lists.sourceforge.net
Subject: Re: [E
Regards,
Marcin
From: Richard Cochran
Sent: 26 February 2021 16:15
To: Miklas, Marcin
Cc: linuxptp-users@lists.sourceforge.net
Subject: [EXTERNAL] Re: [Linuxptp-users] Persistent gPTP Values
[EXTERNAL EMAIL]
On Fri, Feb 26, 2021 at 11:32:21AM +, Miklas, Marcin via Linuxp
Hi all!
In "Automotive Ethernet AVB Functional and Interoperability Specification"
https://avnu.org/wp-content/uploads/2014/05/Auto-Ethernet-AVB-Func-Interop-Spec_v1.6.pdf
there is requirement "6.2.2 Persistent gPTP values". I would like to
implement the persistent neighborPropDelay which can
