On Fri, Apr 17, 2020 at 06:47:57AM +0000, Christian Leeb wrote: > ok. So far. But the CLOCK_REALTIME is not added to list of dst clocks! As a > consequence, CLOCK_REALTIME is not synced anymore. > > phc2sys[1530254.251]: eth0 phc offset -89483 s0 freq -9955 > phc2sys[1530256.350]: eth0 phc offset -39106 s0 freq +34863 > > Is this the intended behaviour?
I'm not 100% sure what was intended. This program grew over time, but I can certainly come up with an explanation for this behavior... Originally, the phc2sys program did something very simple, namely just synchronizing the system clock to a single PHC (or the reverse). When the program grew to support multiple PHCs, then it had to determine which PHC was the slave and synchronize everything else to it. But if no PHC in the slave state, what then is the correct choice? The best choice might be to simply let the system time act as a free running clock. After all, perhaps the motherboard has a quartz crystal and the PHC has a simple R/C circuit. The system clock could very well have better holdover qualities than the PHC. So you might not like this explanation, but there it is. Thoughts? Thanks, Richard _______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
