| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Most of the bulk of this one is the xgpsspeed code, which was not
formerly incldecd in reindenting.
|
| |
|
| |
|
|
|
|
|
| |
special-case the preamble check, undo inversion and shift data bits.
the rest of the words can be properly parity checked.
|
| |
|
| |
|
|\
| |
| |
| |
| | |
Conflicts:
subframe.c
|
| |
| |
| |
| |
| | |
No need to do the painful and confusing hamming code checks if the
preamble is flat wrong.
|
| | |
|
|/
|
|
|
|
|
| |
- whitespace cleanups
- documentation cleanups
- attempt to make frame processing more generic
- add a consistent "50B" prefix to debug messages
|
|
|
|
|
| |
SiRF had. ubx probably the same. So pulled the 50BPS parity checking
into a common subroutine for common use.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
don't reprint the NAV message after stripping the HOW and TLM words
add the "50B" prefix to leapsecond info lines
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Then the reported time is 15 seconds off for a few hours.
Try to catch and prevent that.
|
|
|
|
|
|
|
| |
That is, instead of sectioning out two little config defines and
putting them in. This makes gpsd.h self-copntained (e.g. in case it
gets installed as a library header) and means we can get rid of most
inclusions of it.
|
|
|
|
| |
All regression tests pass.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
...for doing their own parity and inversion checks. Most chipsets do
this already so it's not an onerous burden on driver writers. It has
to be on a per-driver basis because of the inconsistent format each
protocol gives us.
Fix some comments.
Decode gps system message too.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
...for those who want to build their own apps linked against libgps and
want the headers to work. Works on OpenBSD, tested by Jeff Francis on
OS X and Linux
|
|
|
|
| |
First line where possible, second line for scripts called with #!
|
| |
|
|
|