summaryrefslogtreecommitdiff
path: root/HACKING
diff options
context:
space:
mode:
authorEric S. Raymond <esr@thyrsus.com>2005-07-13 22:45:00 +0000
committerEric S. Raymond <esr@thyrsus.com>2005-07-13 22:45:00 +0000
commite2189fad2bc8f94229dc1d0038deef3f8f3ac027 (patch)
tree91572b3f6f7a90dcf26c88e8da34d69f72234c9f /HACKING
parentadd7a2bac6aa5c560c0d3c71229bfc9331e3a37d (diff)
downloadgpsd-e2189fad2bc8f94229dc1d0038deef3f8f3ac027.tar.gz
Update some documentation.
Diffstat (limited to 'HACKING')
-rw-r--r--HACKING14
1 files changed, 14 insertions, 0 deletions
diff --git a/HACKING b/HACKING
index b854488e..bb756bf3 100644
--- a/HACKING
+++ b/HACKING
@@ -480,6 +480,20 @@ strings live in vendor-specific namespaces (PSRF for SiRF, PGRM for
Garmin, etc.) your initializing control string will almost certainly
be ignored by anything not specifically watching for it.
+*** Initializing time and date
+
+Some mode-changing commands have time field that initializes the GPS
+clock. If the designers were smart, they included a control bit that
+allows the GPS to retain its clock value (and previous fix, if any)
+and for you to leave those fields empty (sometimes this is called "hot
+start").
+
+If the GPS-Week/TOW fields are required, as on the Evermore chip,
+don't just zero them. GPSes do eventually converge on the correct
+time when they've exchanged handshakes with enough satellites, but the
+time required for convergence is proportional to how far off the
+initial value is. So make a point of getting the GPS week right.
+
*** How drivers are invoked
Drivers are invoked in one of three ways: (1) when the NMEA driver