| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
All regression tests pass. PPS is live.
|
|
|
|
| |
This logging level is intended to directly explain accompanying I/O messages.
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
On OS X, /usr/include/sys/termios.h typedefs speed_t as unsigned long.
On Linux, it is an unsigned int. This causes printf() format string warnings.
Fix this by down-casting to an unsigned int and using "%u" as format.
Also discard a close() result.
Signed-off-by: Beat Bolli <bbolli@ewanet.ch>
Signed-off-by: Eric S. Raymond <esr@thyrsus.com>
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Introduced in commit 470b53e846f13ab1c660cd05fe901d1e801df4e3.
Signed-off-by: Eric S. Raymond <esr@thyrsus.com>
|
| |
|
|
|
|
| |
Signed-off-by: Eric S. Raymond <esr@thyrsus.com>
|
|
|
|
| |
Signed-off-by: Eric S. Raymond <esr@thyrsus.com>
|
|
|
|
| |
Originator withdrew the patch after noticing his assumptions were wrong.
|
|
|
|
| |
Signed-off-by: Eric S. Raymond <esr@thyrsus.com>
|
| |
|
|
|
|
| |
Signed-off-by: Eric S. Raymond <esr@thyrsus.com>
|
|
|
|
| |
Signed-off-by: Eric S. Raymond <esr@thyrsus.com>
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
|
| |
...and guard them with debug level so they won't be done when the output would
never be shipped anywhere.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
All regression tests pass, splint passes.
|
|
|
|
| |
gpsd.xml gone through
|
|
|
|
|
|
|
| |
Cherry-picked from Jon Schlueter's commit of 2011-03-01 06:38:31.
All regression tests pass.
Signed-off-by: Eric S. Raymond <esr@thyrsus.com>
|
| |
|
| |
|
|
|
|
|
| |
Replace it wuth what it calls, gpsd_write(). Requiresd only a prototype
tweak and some casts, no logic changes. All regression tests pass.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit 2af953aba0cd88a211c0999ac9f49c31e1a34b52.
There really IS a difference between the Garmin Serial Binary (GSB) and
Garmin USB Binary (GUSB).
GSB can do NMEA, GUSB can not
GSB can switch serial speed, GUSB can not
GUSB replaces the kernel driver with libusb, GSB must not.
There is likely more consolidation that can be done, but it should be
done by someone that can test the changes.
|
|
|
|
|
|
|
| |
garmon_ser_binary could never be found by any recent version of the
driver-switching logic, which searches by numeric packet type. It
effectively duplicated garmin_usb_binary, with the same packet type
but earlier in the list.
|
| |
|
| |
|
|
|
|
| |
All regression tests pass.
|
| |
|
| |
|
| |
|