On 25/11/2012 21:37, Dave Hart wrote:
[]
Jitter is a measure of the variability of the phase offset across up
to eight entries in the clock filter register of the selected peer,
the best sample of which ends up as the third column of loopstats.
For a LAN peer best is lowest delay. For PPS, it's
In article k6jeah$ri$1...@dont-email.me, david-
tay...@blueyonder.co.uk.invalid says...
On 28/10/2012 08:28, Rob wrote:
David Taylor david-tay...@blueyonder.co.uk.invalid wrote:
First problem with gpsd resolved, I needed a -n on the command-line!
Next step is to see how the time a GPIO
On 26/11/2012 14:12, DaveB wrote:
[]
Ah, but it does, on the GPIO port, but it's logic is at 3.3V levels, not
even TTL, so take care.
I've yet to make use of it myself though, and I forget what it shows up
as in Linux.
I did find however, that the LAN port has some strange latency
behaviour,
Dave Hart wrote:
I'd appreciate others taking a look at their loopstats on Linux
systems and especially non-x86 Linux to see if 0.0 shows up in
the jitter (fifth column). I think we need more information to
understand the problem.
My Pi ntp server ... syncing to other ntp pool
David Taylor wrote:
server reached over the LAN to have an offset of -0.028 milliseconds,
whereas its own PPS source is reported to have an offset of -0.001
milliseconds. Is that the right sign and amount for the offsets you
might expect comparing the LAN input and the GPIO pin interrupt for
A project for everyone with a spare compatible ar71xx-based router with OpenWRT
12.09 and a PPS source:
http://code.google.com/p/openwrt-stratum1/
___
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
On Mon, Nov 26, 2012 at 1:27 PM, Dave Morgan mor...@eclipse.co.uk wrote:
Dave Hart wrote:
I'd appreciate others taking a look at their loopstats on Linux
systems and especially non-x86 Linux to see if 0.0 shows up in
the jitter (fifth column). I think we need more information to
