"Dave Hart" <[email protected]> wrote in message
news:[email protected]...
[]
It used to be the case that drivers that implemented their own PPSAPI
handling, including the NMEA driver (20), relied on code in the ATOM
driver (22) to filter the PPS samples over a polling interval into a
single offset. Last April, Dr. Mills relocated that code to
ntp_refclock.c in new common PPSAPI handling code used by several
drivers, including the Spectracom/WWVB driver, NMEA driver, ATOM
driver, and to some extent, the parse drivers.
The driver which supports PPS independent of any other timecode/
refclock is the ATOM driver, number 22. The PPSAPI code in 4.2.6's
ATOM and NMEA drivers is essentially the same, the difference is
whether it's used independently or associated with a NMEA source.
Used independently, there must be at least one other source marked
prefer.
Cheers,
Dave Hart
Dave,
Many thanks for this - you have a closer and much clearer view of the code
than I do, and I'm sure your replies will help David Lord as well. Much
appreciated.
If I have understood what you say correctly, then I don't quite see what
use is served by specifying the ATOM driver in addition to the current
(4.2.6 or later) NMEA driver (with a PPS signal fed to the serial port).
Or is my view being hampered by the existence of the kernel-mode serial
driver for Windows?
Thanks,
David
_______________________________________________
questions mailing list
[email protected]
http://lists.ntp.org/listinfo/questions
