I am replying from the digest, I apologize if the message threading is broken from that. ... > And compare ingress_time to the timestamp I get when I use the local > hardware clock (which I am not allowed to sync with ptp). ... > For now all I need is the exact difference between what PTP would deliver > compared to the local systemtime.
You should make sure what exactly you are not permitted to sync with ptp. Is it really hardware clock, or do you mean system clock and RTC? In PTP context when you use the term "hardware clock" I think most would assume that means the PTP Hardware Clock (PHC) in the network controller. To most system administrators the term "hardware clock" would probably imply the system clock maintained by the operating system using processor counters, and synchronized to the realtime clock (RTC) on shutdown, and possibly periodically while running. As far as I am aware the PHC in the NIC is not used for anything other than network time synchronization using PTP, and the PHC has no relation to the system clock unless you also run phc2sys to transfer time from the PHC to the system (software) clock. So in summary it would be worth checking that you and whoever made the restriction of not changing the hardware clock are really speaking of the same thing, because a reasonable interpretation could be that you can sync the NIC hardware clock using PTP, but just don't touch the system clock running from the processor counter. -- Chris Caudle _______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
