| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
...so the packet sniffer no longer needs to take an argument that is
an rtcm structure. This is a step towards a new and better gpsfake.
No logic or protocol changes. All regression tests pass,
|
|
|
|
| |
Teach the daemon to ignore comment packets led with # and ended with \n.
|
|
|
|
| |
problems created by the last big refactoring patch.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a big, super-intrusive patch but changes no logic at all --
it's all about ripping out some of the gps_device_t structure members
into a new gps_packet_t structure. Even the driver API doesn't change
at all, this is all libgpsd(3) internals being rearranged.
The motivation here is that we want to kill off the ad-hoc Python
implementation of a packet-sniffer in gpsfake. To do that we need to
be able to write a "pure" packet sniffer that uses the same C code as
the daemon's but without being welded to the rest of the libgpsd(3)
code. This is the first step towards that.
|
|
|
|
|
| |
This diff makes that happen, and tries to be forthcoming about
when it is making gpsd run as root.
|
| |
|
|
|
|
|
| |
...we should do the same when setting up the OpenBSD-specific
timestamping code.
|
|
|
|
|
|
| |
Nest appropriately so we can compile on 4.0. Also log correctly so
that users wondering why the sensors don't seem to be working will
have something in their logs.
|
|
|
|
|
|
|
|
|
|
|
|
| |
In recent versions, the kernel keeps timestamps of control line
changes. We also have the nmea(4) line discipline which activates an
in-kernel NMEA parser to extract time information. This is then
exported via the sensors framework for use by openntpd.
This partially worked, but it wasn't until this morning that we had the
control line stuff working.
CK
|
|
|
|
| |
...the same way probe_subtype does, and for the same reason.
|
|
|
|
|
|
| |
The EverMore probe should just flip us into binary mode. Petr gaves me
a heads-up that he's already done this removal in his experimental
sources.
|
| |
|
|
|
|
|
|
| |
...that causes the driver's mode switcher to be invoked just after the
revert method. This makes the revert methods for SiRF and EverMore
unnecessary.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
regarding when garmin/nmea should be enabled.
|
|
|
|
| |
Allow the garmin stuff to compile without NMEA
|
| |
|
|
|
|
|
| |
I'm going to have to do another single-protocol compile test soon,
though Mick seems to be doing that for me. Thanks!
|
| |
|
| |
|
|
|
|
| |
if configuration is enabled.
|
|
|
|
|
|
|
| |
It turns out the ZDA sentence we wanted is in their default output
set. We'll allow users who've turned ZDA off explicitly to have a
century-rollover problem in exchange for not stepping on other
settings.
|
|
|
|
| |
undo switch to SiRF binary on close if driver started in SiRF NMEA.
|
| |
|
|
|
|
| |
...so we don't see stale data. Also, some splint cleanup.
|
|
|
|
|
|
|
|
| |
1. Use libxslt for the correct dependency in the spec file.
2. Fix somedocumentation typos.
3. Fix gpsctl man page as suggested by Pert Slansky.
4. Suppress leading zeros in xgps satellite-data display.
5. Change "Course" to "Track" in xgps display.
|
| |
|
| |
|
| |
|
|
|
|
| |
But adapt to the new API just in case.
|
|
|
|
| |
daemon and is the last piece in making gpsctrl work for SiRF chips.
|
|
|
|
|
| |
This avoids confusion by devices like SiRFs in NMEA
that echo unknown probe strings back at us.
|
| |
|
| |
|
|
|
|
|
| |
*immediately* improve detection of SiRF devices in NMEA mode, and probably
solves Davor Emard's Garmin GPS-10 bug as well (though this is not yet proven.
|
|
|
|
|
| |
between our LOG_ERR and the syslog() macro by changing ours to
LOG_ERROR.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch defines a uniform set of log levels and changes all gpsd_report()
instances to use them. In most cases (I'd say about 80%) this will make
no observable difference, as the numeric log levels the code was using were
not too badly inconsistent anyway. The new log level macros are defined
and described in gpsd.h.
The main thing I wanted was to be able to consistently force dumping
of all I/O to devices and clients with -D 4. Some drivers didn't honor
this. One or two still may not through lack of an internal write() wrapper
that does logging; there will need to be some followup changes.
Level 0 messages are always displayed, but to make the semantics clearer
there are two defines LOG_ERR and LOG_SHOUT.
Level 5 is still super-raw I/O reporting. Level 6 and 7 messages are
tagged RAW_LOG+1 and RAW_LOG+2; I was particularly careful about these
because we have one report of a user who is getting good results from
Garmin serial only at -D 7 or up, and perish forbid I should interfere
with that bug being found.
|
|
|
|
|
| |
...whether or not they actually do anything. Otherwise it may not
have the right value when somebody queries it.
|
| |
|
|
|
|
|
|
|
| |
...with the grotty internal baud-hunting loop and without the attempt
to merge tnt_send with nmea_send or use of the wakeup capability. If
Massimo Burcher can get this working, we'll try mutating it forward
again.
|
|
|
|
|
| |
Implement mode holding in the server when J=1 is on.
Small splint cleanups.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
There is now a new method, "configurator". The initializer method
probes the driver for subtype information (such as a firmware rev)
without changing any device settings. The configurator method does
things like selecting which packets should send.
At the moment, these two methods are always called in tandem, so there
has been effectively no change in behavior. Soon, though, gpsctrl
will call the initializer method but *not* the configurator.
|