On Fri, May 24, 2013 at 8:14 PM > From: Hal Murray >> Besides I got them to run NTP and they're too jittery for my taste. > > How good/bad were they? The view from the RPi*: server (local remote refid st t when poll reach delay offset jitter ============================================================================================ 127.0.0.1 o127.127.22.0 .PPS. 0 l - 8 377 0.000 -0.001 0.003 192.168.0.192 *192.168.0.2 .PPS. 1 u - 8 377 0.460 -0.003 0.037 192.168.0.192 +192.168.0.210 .GPS. 1 u 7 8 377 0.920 -0.019 0.202 192.168.0.192 +192.168.0.244 .PPS. 1 u 7 8 377 0.493 0.022 0.031
The view from a mini-itx/Atom system: server (local remote refid st t when poll reach delay offset jitter ============================================================================================ 127.0.0.1 o127.127.22.0 .PPS. 0 l 1 8 377 0.000 0.000 0.002 192.168.0.244 +192.168.0.2 .PPS. 1 u 8 8 377 0.085 0.004 0.002 192.168.0.244 +192.168.0.210 .GPS. 1 u 7 8 377 0.544 0.001 0.216 192.168.0.244 *192.168.0.192 .PPS. 1 u 6 8 377 0.485 -0.008 0.025 One odd system is enough. > What were you using for a time source? Does it have PPS support? I have a variety of PPS sources. The RPi is most often connected to a Sure dev. board. David Taylor linked to Hauke Lampe who did a kernel build with PPS drivers. *The tables look okay here but are probably trashed there. _______________________________________________ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.