On 23/09/2023 02:18, allan edwards wrote:
> Does anyone have a unicast ptp setup guide?
>
> I read the docs but nothing points to the table you create for unicast
> and the settings and how they should look. Did I miss this in the docs?
>
You can find an example in the configs folder:
https://
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 6/2/2023 9:01 PM, Trey Harrison wrote:
> Subject kinda says it all.. We have previously been using chrony to
> synchronize systems on a network, and chrony allows slave devices to
> specify the ip address of their clock source.
>
> It does not seem obvious after reviewing documentation here t
> On 28 Nov 2022, at 23:30, Nemo Crypto wrote:
>
> Hi All,
> I found that Rasberry Pi CM4 has support for PTP timestamping. It has Gigabit
> Ethernet PHY with IEEE 1588 support.
> If anyone is using the same and running ptp4l on it, please respond. We can
> collaborate.
> Thanks :)
>
Linux
The ntpshm servo will put results in the shm and let the other entity
to control the clock - hence it doesn't lock itself and always returns the
SERVO_UNLOCKED. I'd recommend setting up ptp4l with one of regular
servos and use the phc2sys to transfer the offset to the NTP daemon.
Regards
Maciek
>
Nope, I think it's more about the clock_servo option. Free-running
will not do anything to the clock.
clock_servo
The servo which is used to synchronize the local clock. Valid values
are [...] "nullf" for a servo thatalways dials frequency offset zero
(for use in SyncE nodes).
Regards
Maciek
> -
