summaryrefslogtreecommitdiff
path: root/gpsd.xml
diff options
context:
space:
mode:
authorEric S. Raymond <esr@thyrsus.com>2005-05-20 21:32:34 +0000
committerEric S. Raymond <esr@thyrsus.com>2005-05-20 21:32:34 +0000
commitc60f328fbf9a3e477996eda951669d1e8300f476 (patch)
treef2af6675c215ff6e84f39ca0bbcaf05cbe53baa9 /gpsd.xml
parent3b7496d15320746c2f8e7abb5554a837ac70c95b (diff)
downloadgpsd-c60f328fbf9a3e477996eda951669d1e8300f476.tar.gz
Documentation fixes.
Diffstat (limited to 'gpsd.xml')
-rw-r--r--gpsd.xml7
1 files changed, 7 insertions, 0 deletions
diff --git a/gpsd.xml b/gpsd.xml
index b8ea036a..9d69e5b1 100644
--- a/gpsd.xml
+++ b/gpsd.xml
@@ -732,6 +732,13 @@ by the chip. The computation does not exactly match what SiRF chips
do internally, which includes some satellite weighting using
parameters <application>gpsd</application> cannot see.</para>
+<para>If you are using an NMEA-only GPS (that is, not using SiRF or
+Garmin or Zodiac binary mode) and the GPS does not emit GPZDA at the
+start of its update cycle (which most consumer-grade NMEA GPSes do
+not) and your system clock is zeroed or set incorrectly, then the
+century part of the dates <application>gpsd</application> delivers
+will be wrong.</para>
+
</refsect1>
<refsect1 id='files'><title>FILES</title>