| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
| |
All regression tests pass.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
...splint needs some pacifying. This is part 1. All regressions pass.
|
| |
|
|
|
|
|
| |
Solaris lacks u_int*_t typedefs. Switch to the C99 standard ones. All
regression tests pass.
|
|
|
|
|
|
|
| |
On NMEA devices, mode could sometimes be held across cycles when it
shouldn't have been. Fix this, simplifying how cycles are tracked in
the process. Some regression tests needed rebuilding. Code splints
clean.
|
| |
|
|
|
|
|
| |
...making the regression tests nondeterministic. Oh well. Fixed.
All drivers now use the LOG_DATA convention.
|
|
|
|
|
|
|
|
| |
There was lots of duplicative setting of gpsdata.fix.time and
gpsdata.sentence_time. The latter is now gone. The only case the
sentence_time member was actually used for was timestamping skyviews;
a new gpsdata.skyview_time now handles that, and all drivers set it
properly.
|
|
|
|
| |
All regression tests pass, code splints clean.
|
|
|
|
|
|
|
|
|
|
|
| |
This had the expected effect, the N command can now works on SiRFs
again because the subdevice probe is not called after every driver
switch.
One of the Trimbles has minor regression breakage on this change
(two fewer reports emitted just after packet lock) but I'm not
worrying about that as the TSIP driver needs to be upgraded to
do CYCLE_END, anyway.
|
| |
|
|
|
|
|
|
| |
...mainly because there will shortly be code to clear it as a unit.
Pure refactoring step; all regression tests pass, splint gives no
warnings.
|
|
|
|
|
| |
this resulted in some spurious reports. Required rebuilding of the
TSIP regression check logs. All other regression tests passed.
|
| |
|
|
|
|
|
|
|
| |
This finishes the bug refactoring; now we're ready to do actual
behavior changes.
Codebase splints clean. All regression tests pass.
|
|
|
|
|
| |
Abolish the wrapup method; there were only two users, one
was trivial, and the other belonged as a revert.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Code that referenced the sequence number argument now looks at
session->packet_counter directly.
This was almost a pure refactoring step. I added one obviously
missing session->packet.counter == 0 test in the oncore driver.
Despite temptation, I didn't try to fix when the packet.counter
gets zeroed; I'm going to try to confine the behavior changes
to one concise patch, which hasn't happened yet.
Codebase splints clean. All regression tests pass.
|
|
|
|
|
|
|
| |
They're now distinguished by an event argument passed to the common
hook function. This is a refactoring step - later, we'll define more
and different events for finer-grained control. All regression tests
pass.
|
|
|
|
| |
No effect on compilation. All regression tests pass.
|
|
|
|
|
| |
Major change in this set is enforcong consistency about the data type
of serial parity information.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
and the fact that its cycle end indication is reliable. All
regression tests pass.
|
|
|
|
| |
Refactoring step, no behavior changes. All regression tests pass.
|
|
|
|
|
| |
...documented in the protocol-transition white paper. All regression
tests pass.
|
|
|
|
| |
Currently this messes with the serial speed and modes. It shouldn't.
|
|
|
|
|
|
| |
That way of doing things coped poorly if, for example, NMEA and AIVDM
packets were reported over the same wire. Instead, have ach device
track the packet types it has actually seen and dispatch on that.
|
| |
|
|
|
|
|
| |
the Copernicus), but they should nicely reject the poll. Lassen iQ doesn't
document this message, but mine does emit it...
|
|
|
|
|
|
| |
it can store all integer values we're likely to see, plus the floating
point values that some protocols use in their raw measurement
messages. regression tests still pass.
|
| |
|
|
|
|
|
| |
>From Matt Roberds on gpsd-users
http://marc.info/?l=gpsd-users&m=124416116419553&w=2
|
| |
|
|
|
|
|
|
|
| |
It was only ever being set to constant 1. Instead, we keep the
current cycle in gpsdata and initialize it in gpsd_init(). This makes
no behavioral changes, but clears the decks for better handling of
rate switchers.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
It now conditions out the speed-switcher, mode-switcher, and
rate-switcher methods of the driver structure entirely. This makes it
possible to condition out whole functions (rather than small bits that
do device writes) almost everywhere. Build tested with
ALLOW_RECONFIGURE off.
This improvement should make the embedded people happy.
|
| |
|
|
rename the packet drivers to driver_$(protocol).c
|