| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
|
|
|
|
|
| |
This makes each packet handler dump the fields that it touched and the
validity mask. The NMEA, Evermore, and GTXT drives now use this. No
behavior changes. All regression tests pass.
|
|
|
|
| |
All regression tests pass.
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
All regression tests pass.
|
|
|
|
|
|
| |
...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 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.
|
| |
|
|
|
|
|
| |
Some regression tests needed to be rebuilt as a result.
One new regression test, for iTalk binary.
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
|
|
|
| |
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
|