On 09/12/2014 20:51, Paul wrote:
[]
As I mentioned previously it's still possible to use refclock 1 (LOCAL).
The driver is claimed to be deprecated but it's still present in 4.2.7 so
presumably will be in 4.2.8.
server 127.127.22.0 minpoll 3 maxpoll 3
fudge 127.127.22.0 stratum 0
server
On Tue, Dec 09, 2014 at 03:29:45PM +0100, Sander Smeenk wrote:
I run a stratum 1 server which has a Garmin LVC 18x connected to its ttyS0.
The GPS provides a PPS signal via serial and i use gpsd to provide the
NMEA sentences and pulse data in shared memory to NTP.
This partly works. NTP
On 10/12/2014 10:24, Miroslav Lichvar wrote:
[]
If it's a recent version of gpsd which uses kernel timestamps (check
for KPPS messages in gpsd -D 4 output), you may already have a true
PPS sync. The PPS and NMEA timestamps are paired in gpsd, so it's not
necessary to add the NMEA source to ntpd.
On Wed, Dec 10, 2014 at 11:50:22AM +, David Taylor wrote:
With -D 4 I get a list of devices ending with PPS, but presumably that is
not the same as KPPS?
In gpsd the PPS without K is the userspace timestamping. With kernel
timestamping the log looks like this:
gpsd:PROG: PPS edge: 1,
On Wed, Dec 10, 2014 at 5:04 AM, Miroslav Lichvar mlich...@redhat.com
wrote:
See also the following post, apparently the BBB can use a separate HW
timer to timestamp PPS, reducing the error and jitter significantly.
http://blog.dan.drown.org/beaglebone-black-timer-capture-driver/
It looks
