diff options
| author | Eric S. Raymond <esr@thyrsus.com> | 2015-04-01 14:22:34 -0400 |
|---|---|---|
| committer | Eric S. Raymond <esr@thyrsus.com> | 2015-04-01 14:23:25 -0400 |
| commit | 3d64ec6442cd7a7dcdd03a4f8df6eb9c8da7c9f5 (patch) | |
| tree | b72f91081780ca3d21ce380965102571d2067002 /TODO | |
| parent | ceba717184bf78aa5435f8051510e7439872e6d5 (diff) | |
| download | gpsd-3d64ec6442cd7a7dcdd03a4f8df6eb9c8da7c9f5.tar.gz | |
Remove an impossible FIXME and an ill-specified TODO. No code changes.
Diffstat (limited to 'TODO')
| -rw-r--r-- | TODO | 9 |
1 files changed, 0 insertions, 9 deletions
@@ -94,15 +94,6 @@ Our goal is to be independent of the system clock. See <http://www.febo.com/pipermail/time-nuts/2013-August/079271.html> -**** Track gpsd's confidence in the GPS time it's seeing - -This would increase when we see a leap-second offset or get GPZDA from -the device, decrease when we detect a rollover. Some devices that are -known to deliver high-quality time (notably u-blox GPSes) would peg the -confidence measure at a high level. We'd use the confidence level to -control (a) whether gpsd ships to NTP, and (b) how it sets time -uncertainty in output JSON. - *** Optionally use tag blocks in NMEA output Ed W. writes: |