| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
This enables us to force readonly off while it's being called.
The practical effect is that gpsmon can get a firmware version (if this
is possible) without reconfiguring the device.
|
|
|
|
|
|
|
| |
Required a regression-test rebuild, of course. The field is still set by
the TSIP and SiRF drivers; the SiRF driver actually uses it. It may be
possible to eliminate the TSIP uses, but so far attempting this has
produced odd regression-test failures.
|
|
|
|
|
|
|
|
|
|
| |
Way too much logging was happening at LOG_IO level, which is intended for
watching data traffic in and out of the daemon rather than all the minutiae
of data analysis - that's LOG_DATA.
Also, LOG_DATA gets pushed down two levels. The effect is that -D 5
means exactly what it did, but for purposes other than driver debugging
-D 4 now suffices.
|
| |
|
|
|
|
|
|
|
| |
Because it might be going to chrony. Or something else.
No logic changes, just name changes and one new derived #define,
TIMEHINT_ENABLE.
|
|
|
|
| |
We'll have to sneak up on this change more slowly.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
ntp_offset becomes time_offset. There is a new config symbol CHRONY_ENABLE;
most time service code is npw controlled by TIMESERVICE_ENABLE. The
file ntpshm.c becomes timeexport.c
This change is not complete. More disentanglement has to be done inside
timeexport.c itself; at the moment enabling one but not both of
ntpshm or chrony will probably break its compile. The point of getting
this commit out is so Gary will see the new baseline code ASAP.
All regression tests pass.
|
| |
|
| |
|
| |
|
|
|
|
| |
...rather than setting it ad-hoc on a per-driver basis.
|
|
|
|
|
|
|
|
| |
This is a large, ugly change. But without it we can't troubleshoot the
ICP/IP-source initialization bug properly - colliding definitions of
gpsd_report() were interfering with error reporting early in gpsd runs.
More cleanup work remains to be done, but at least this is working.
|
| |
|
|
|
|
|
|
| |
...and be more explicit about operand sizes.
All regressuion tests [ass, code splints clean.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Enable binary support when navcom driver is enabled, otherwise the build
errors out with:
./libgpsd.so: undefined reference to `navcom_binary'
If no other drivers needing binary support are enabled.
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
Signed-off-by: Eric S. Raymond <esr@thyrsus.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This awkward construct seems to have triggered some sort of toolchain
bug. The symptom is that gpsd_hexdump_level has different values depending
on whether we test it inside or outside of hex.c.
As a first step towards eliminating this global, we throw out a bunch
of hex logging that is duplicative or not really needed for production
drivers. Experimental drivers can call the hex dumper unconditionally.
The goal is to reduce the number of uses of this variable to eliminate it
withoud doing violence to the internal APIs. This is a first step.
All regression tests pass.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Required so clients looking at flag masks in data exported via the shared-memory
interface will see the right thing.
These were separated originally in order to avoid pushing the reqyuired width
of the gpsdata.set flag mask over 32 bits. It became 64 bits in the Version 5
API change, so that constraint went away.
All regression tests pass.
|
|
|
|
| |
All regression tests pass.
|
| |
|
|
|
|
|
| |
Replace it wuth what it calls, gpsd_write(). Requiresd only a prototype
tweak and some casts, no logic changes. All regression tests pass.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
All regression tests pass.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
The Navcom protcol reference tells us that the factory default is to stream
GGA & VTG at 1Hz, 19.2Kbps. Therefore it doesn't need a wakeup before it
sends data. It also teklls us that settings are hewld in NVRAM so we
don't need to redo them on reactivate.
|
|
|
|
|
|
| |
With most machines being 64-bit now, the assumption that "word" = 16 bits and
"long" = 32 bits is increasingly archaic. This commit removes it from our
naming conventions.
|
| |
|
|
|
|
| |
All regression tests pass.
|
| |
|
|
|
|
|
|
|
|
|
| |
Drivers shouldn't really set this any more, as it's used to signal that the
attempt to get sync on a data stream has failed.
Also, make some UDP cases wirk bewtter by arranging not to throw ERROR_IS on
leading comments. No, I don't know why this didn't fail sooner. It must have
sommetthing to do with the granularity of the writes from ptys
|
| |
|
| |
|
|
|
|
|
| |
Most of the bulk of this one is the xgpsspeed code, which was not
formerly incldecd in reindenting.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This solves the disappearing epx/epy bug on SiRFs, but it was actually a
systemic problem that affected several drivers. Navigation solution messages
were clearing DOPs, making it impossible for the error modeller to compute
estimates. New logic: Clear DOPs only when we get a skyview report. They'll
be regenerated by our visibility-matrix calculation when the skyview sentence
is analyzed.
If a sentence from the device supplies a DOP between the time the visibility
calculation is done and when the next fix is reported, it will override
our computed value. This might change later!
This change required a regression-test rebuild.
|
| |
|
|
|
|
| |
sesion->context.
|
|
|
|
| |
Prepare to do the same for Time of Week (tow).
|
| |
|