| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
Only once a second.
|
|
|
|
| |
This makes it easy to pick oout the time logs. Along with PPS:
|
|
|
|
| |
/dev/pps0 actually seems to work.
|
|
|
|
|
|
| |
/dev/pps0 now ships time to NTP SHM. Very wrong time...
last_fixtime is all wacky...
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Instead, pass out real time of last PPS as it was actually seen. We can then
correct it using the device's actual cycle time.
The correction currently only works for cycle times that are integral
multiples of a second.
|
|
|
|
|
|
| |
Remove the wrap hook. The only thing it was doing was closing the chrony fd.
which can be done just as cleanly by whatever calls the pps_thread_deactivate()
function.
|
|
|
|
|
|
| |
With a bit of refactoring we can eliminate one of the hooks.
PPS observed live, telnetting to localhost:2947 with gpsd running.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The proximate cause was that we've been seing emission of error
messages that were randomly and disturbingly variable across different
environments - notably Raspbian and Gentoo splint gave nontrivially
different results than Ubuntu 14.10 splint. And this was *not* due to
Ubuntu patches! A pristine splint built from the 3.1.2 tarball on
Ubuntu didn't match the Raspbian and Gentoo results either.
But this has been coming for a while. Easy access to more modern
static analyzers such as coverity, scan-build and cppcheck has been
decreasing the utility of splint, which is unmaintained and somewhat
buggy and not easy to use.
Only file not cleaned is ppsthread.c, because Gary has been working
on it during this cleanup.
All regression tests pass. PPS observed live on GR601-W.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
With more than one PPS thread going at a time hard to know
which is which without help.
Also remove restriction that devicename is a tty since /dev/ppsX is
not a tty.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Same fix as in ntpshmwrite.c. GPS may notify about upcoming
leap second long before NTP can handle it. So limit leap notify to
months of June and December.
Per Hall Murray and http://bugs.ntp.org/1090
|
| |
|
|
|
|
|
|
| |
It's not used on the client side, and it's needed separately for ntplib.
All regression tesrs pass. PPS is live.
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is the big step towards ntplib. A couple of minor issues remain to be
ironed out, the most significant of which is what to do about the timestamp_t
type.
This changes some field offsets of private fields in struct gps_device_t.
Probably does not require a version bump as access to them is all through
the libgpsd API.
All regression tests pass. PPS observed live in gpsmon direct mode.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change is done so we can add a "log" hook to the pps_thread_t
structure (this is not done yet) and harmonize with the name of the
outer logging function. If that name had been left as gpsd_report()
there would have been scope for bad confusion with the report_hook
member.
Also, remove two stray duplicative printf calls from the NMEA2000 driver
(drivers shouldn't have printfs!) and fix one typo.
This is a step towards factoring out ntplib. For that to happen, the
PPS thread code needs to be decoupled from the core session structure.
No logic changes. Object compatibility preserved. All regression tests pass.
|
|
|
|
|
|
|
|
|
|
|
| |
No logic changes, though it looks like there are two because two guards
that would always have failed when the code was compiled with pps=off
are now conditioned out. Also, this code is offset-preserving
so as not to break link-time compatibility of libgpsd.
(This is the subtler approach...)
All regression tests pass.
|
|
All knowledge of the ntpd SHM format is now confined to the three
files ntpshm.h, ntpshmread.c, and ntpshmwrite.c.
No logic changes. All regression tests pass. PPS works on GR-601W.
|