summaryrefslogtreecommitdiff
path: root/driver_nmea0183.c
diff options
context:
space:
mode:
authorEric S. Raymond <esr@thyrsus.com>2015-04-07 07:30:41 -0400
committerEric S. Raymond <esr@thyrsus.com>2015-04-07 07:30:41 -0400
commit7373baf5439ce88a1aba3911fc8f005b7ebcd952 (patch)
tree6e5ba3f3722acdb4af09557ae445cede23aef035 /driver_nmea0183.c
parentd5ad9f2f9b219de1d35ef95cd60f7fee67ba9935 (diff)
downloadgpsd-7373baf5439ce88a1aba3911fc8f005b7ebcd952.tar.gz
Document assumptions about NMEA satellite IDs and PRNs more thoroughly.
Diffstat (limited to 'driver_nmea0183.c')
-rw-r--r--driver_nmea0183.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/driver_nmea0183.c b/driver_nmea0183.c
index 774ee61b..6eaa09d5 100644
--- a/driver_nmea0183.c
+++ b/driver_nmea0183.c
@@ -476,7 +476,7 @@ static int nmeaid_to_prn(char *talker, int satnum)
*
* Also see the *_PRN macros in gps.h for a slightly different mapping
* apparently described in IS-GPS-200 Revision H, paragraph 6.3.6.
- * There's a conflict in the 33-64 range.
+ * There's a potential conflict in the 33-64 range.
*
* The issue is what to do when GPSes from these different systems
* fight for IDs in the 1-32 range, as in this pair of Beidou sentences
@@ -502,7 +502,7 @@ static int nmeaid_to_prn(char *talker, int satnum)
/* GLONASS reports don't seem to do this, but better safe than sorry */
if (talker[0] == 'G' && (talker[1] == 'L' || talker[1] == 'N'))
satnum += 37;
- /* QZSS sentences have not been seen in the wild yet */
+ /* QZSS */
if (talker[0] == 'Q' && talker[1] == 'Z')
satnum += 193;
}