| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
SiRF development kit so I don't have to be absolutely terrified of
trashing the receiver.
|
| |
|
|
|
| |
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.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
...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
|
| | |
|
| |
|
|
|
| |
Validate the s-record file before trying to send it to the receiver,
just in case it got corrupted.
|
| |
|
|
| |
Yes, this does mean I'm hacking on firmware loading some more.
|
| |
|
|
| |
First line where possible, second line for scripts called with #!
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
GPSD is now free from the often-misused strcat, strcpy and
sprintf. Future code should not use unbounded string functions. Glibc
users, please verify that the integrated strlcat and strlcpy are
correctly linked in.
|
| |
|
|
|
|
|
|
|
|
| |
1) the product line is called SiRFstar
2) I don't have any original SiRFstar receivers but my documentation
says the protocol remained mostly the same between SS1, SS2 and SS3;
it just got richer as time went by. At least with my SS2 and SS3
receivers, this holds true.
3) elsewhere in the code there are SIRF_THIS and SIRF_THAT, which
implies (correctly) independence of chipset version.
|
| | |
|
| |
|
|
| |
...not that it will do anything useful.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Shouldn't change any actual behavior, except the environment variable
checked now natches the manual page.
|
| |
|
|
|
|
|
| |
In case of improper invocation, don't unlink the program (gpsflash has
no business writing the local filesystem) and don't be rude to the
user. Rather, explain that something could go very wrong, and that you
must read our warnings in the manpage.
|
| |
|
|
|
|
|
|
|
| |
which was wrong. The serialConfig function sets up a number of useful
parameters like flow control, parity checking and VMIN/VTIME.
This only needs to be done once, so we do it right after we open the port.
Other port changes are baud rate only, so we call a different function to
just set the baud rate.
|
| |
|
|
| |
for future use.
|
| | |
|
| |
|
