summaryrefslogtreecommitdiff
path: root/timebase.c
diff options
context:
space:
mode:
authorEric S. Raymond <esr@thyrsus.com>2013-11-26 14:41:59 -0500
committerEric S. Raymond <esr@thyrsus.com>2013-11-26 15:49:36 -0500
commit04c37025062e60d638ca511fc323d9d07090934c (patch)
tree7dcfa1b235cb3c53dc50766c8584af23ccfaf82b /timebase.c
parentbd812b6a1c84ccf5094cf147112ff74ea29b6a3e (diff)
downloadgpsd-04c37025062e60d638ca511fc323d9d07090934c.tar.gz
RAM -> NVRAM.
Diffstat (limited to 'timebase.c')
-rw-r--r--timebase.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/timebase.c b/timebase.c
index 0ad17406..02bbee37 100644
--- a/timebase.c
+++ b/timebase.c
@@ -51,7 +51,7 @@ last rollover) that we don't have access to. Thus, there's no way to
check whether a rollover the device wasn't prepared for has occurred
before gpsd startup time (making the reported UTC date invalid)
without some other time source. (Some NMEA devices may keep a
-rollover count in RAM and avoid the problem; we can't tell when that's
+rollover count in NVRAM and avoid the problem; we can't tell when that's
happening, either.)
2) Many NMEA devices - in fact, all that don't report ZDA - never tell