Thanks guys. This is getting interesting. $ dmesg|grep clock [ 0.255576] hpet clockevent registered [ 0.258069] Switching to clocksource hpet [ 1.155479] rtc_cmos 00:03: setting system clock to 2013-08-17 20:38:33 UTC (1376771913) [ 1.382147] PTP clock support registered [ 7.640035] intel8x0_measure_ac97_clock: measured 54638 usecs (2680 samples) [ 7.640040] intel8x0: clocking to 46972
$ dmesg|grep tsc [ 0.000000] tsc: Fast TSC calibration using PIT [ 0.000000] tsc: Detected 2412.241 MHz processor [ 0.000000] tsc: Marking TSC unstable due to TSCs unsynchronized I guess I can't go with TSC on this hardware. Generally, for now, what I'm asking is... If NTPd is managing the radio and slewing with the PPS, the PTP daemon (ptp4l) will be taking time from the same system source? Granted, PTP time is not the same as Unix time, and maybe I'm not understanding the use of the phc2sys utility? Probably a better question for the linuxptp group. -- David Gravereaux <[email protected]>
signature.asc
Description: OpenPGP digital signature
_______________________________________________ time-nuts mailing list -- [email protected] To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
