summaryrefslogtreecommitdiff
path: root/nmea_parse.c
diff options
context:
space:
mode:
authorEric S. Raymond <esr@thyrsus.com>2009-01-03 15:07:46 +0000
committerEric S. Raymond <esr@thyrsus.com>2009-01-03 15:07:46 +0000
commitfa6f749ece03138cf1ccaa8df48275bafed567a9 (patch)
treeff19b89a9ab06a2669b976c9d35b3e14b1570600 /nmea_parse.c
parent06923ca737908ae0fb4e437c89f2a1c7f15d561c (diff)
downloadgpsd-fa6f749ece03138cf1ccaa8df48275bafed567a9.tar.gz
My change to the scaling of O reports four days ago was backwards.
It was the E report that was wrong. The confidence-interval unit has to be tweaked to 95% at driver level, where we actually have some clue what the device type reports, not messed with in the gpsd.c upper-level code.
Diffstat (limited to 'nmea_parse.c')
-rw-r--r--nmea_parse.c3
1 files changed, 2 insertions, 1 deletions
diff --git a/nmea_parse.c b/nmea_parse.c
index f4d3ec44..4a52441d 100644
--- a/nmea_parse.c
+++ b/nmea_parse.c
@@ -502,7 +502,8 @@ static gps_mask_t processPGRME(int c UNUSED, char *field[], struct gps_device_t
* Garmin won't say, but the general belief is that these are 50% CEP.
* We follow the advice at <http://gpsinformation.net/main/errors.htm>.
* If this assumption changes here, it should also change in garmin.c
- * where we scale error estimates from Garmin binary packets.
+ * where we scale error estimates from Garmin binary packets, and
+ * in libgpsd_core.c wgere we fenerate $PGRME.
*/
if ((strcmp(field[2], "M")!=0) ||
(strcmp(field[4], "M")!=0) ||