On Mon, Jul 11, 2022 at 09:06:12AM +0200, Marco Davids (SIDN) via Linuxptp-users wrote: > Op 09-07-2022 om 08:44 schreef Maciek Machnikowski: > > > 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. > > Right.
To expand a bit on this, there is no information provided back to ptp4l/phc2sys about the state of the clock from the consumer, or whether the samples are actually accepted and used for synchronization. > > I'd recommend setting up ptp4l with one of regular > > servos and use the phc2sys to transfer the offset to the NTP daemon. > > But that wouldn't work iwith software time stamping, would it? It wouldn't. phc2sys is needed when ptp4l synchronizes a PHC. With software timestamping it should be ptp4l using the ntpshm servo. -- Miroslav Lichvar _______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
