I have a Compute Module4 single board computer controlled using
linuxptp to a White Rabbit switch as grand master. The client is
controlled by the server with linuxptp 3.1.1
ptp4l[8729.388]: selected /dev/ptp0 as PTP clock
ptp4l[8729.432]: port 1: INITIALIZING to LISTENING on INIT_COMPLETE
ptp4l[8
On Mon, Jul 10, 2023 at 11:47:00AM +0200, jmfri...@femto-st.fr wrote:
> I have a Compute Module4 single board computer controlled using
> linuxptp to a White Rabbit switch as grand master. The client is
> controlled by the server with linuxptp 3.1.1
> and all goes well. I upgraded to linuxptp 4.0
Hi,
and all goes well. I upgraded to linuxptp 4.0 in order to activate some
of the newer options and now in the exact same context I am unable to
lock with the messages
don't you use automotive profile or 802.1 AS profiles? Because if so,
there was a change in computations of the time differe
"don't you use automotive profile or 802.1 AS profiles?": I am not
(yet) familiar enough with linuxptp to comment. I did not change
anything to the settings, using the default configuration, whatever
that is.
I git bisected and the faulty commit is
2a2532d66121d0060b042c5bd6020a62153f1e0a is the
I actually see a comment about this patch at
https://github.com/richardcochran/linuxptp/commit/2a2532d66121d0060b042c5bd6020a62153f1e0a
stating that
"it seems that this commit breaks compatibility with some GMs, e.g.,
Microchip's TP4100. Tested with G.8275.2 profile. The reason being that
this par
... and I can confirm that the correction proposed at
https://github.com/richardcochran/linuxptp/commit/2a2532d66121d0060b042c5bd6020a62153f1e0a
namely setting the PTP_MINOR_VERSION from 1 to 0 in msg.h returns
proper operation of the PTP client on the current git version of
linuxptp.
Thanks, Jean
On Mon, Jul 10, 2023 at 03:49:52PM +0200, jmfriedt wrote:
> I git bisected and the faulty commit is
> Bump to IEEE 1588-2019 version
I think that means the hardware cannot timestamp PTPv2.1 packets, only
PTPv2.0 packets.
You can change PTP_MINOR_VERSION in msg.h to 0 and see if that helps.
Le 10/07/2023 à 16:29, Miroslav Lichvar a écrit :
On Mon, Jul 10, 2023 at 03:49:52PM +0200, jmfriedt wrote:
I git bisected and the faulty commit is
Bump to IEEE 1588-2019 version
I think that means the hardware cannot timestamp PTPv2.1 packets, only
PTPv2.0 packets.
Something fixable by th
> > I think that means the hardware cannot timestamp PTPv2.1 packets,
> > only PTPv2.0 packets.
> Something fixable by the white rabbit projet as it is a full fpga
> implementation.
Is it the WRS that needs to be updated? their web page says
"Technically, the White Rabbit Network is a Bridged L
On 7/10/2023 4:21 PM, jmfriedt wrote:
> I actually see a comment about this patch at
> https://github.com/richardcochran/linuxptp/commit/2a2532d66121d0060b042c5bd6020a62153f1e0a
>
> stating that
> "it seems that this commit breaks compatibility with some GMs, e.g.,
> Microchip's TP4100. Tested
On Mon, Jul 10, 2023 at 05:37:10PM +0200, jmfriedt wrote:
> Is there a
> rationale for preventing out of the box linuxptp from working with both
> PTP 2.0 and 2.1 packets, since changing the constant in the header file
> seems to make the protocol operational again?
linuxptp works with both ptp v
11 matches
Mail list logo
