diff options
| author | Eric S. Raymond <esr@thyrsus.com> | 2013-09-27 13:34:52 -0400 |
|---|---|---|
| committer | Eric S. Raymond <esr@thyrsus.com> | 2013-09-27 13:34:52 -0400 |
| commit | 718f7af4f049cc44273f89e74fd3dab9510e7478 (patch) | |
| tree | 44c0e2e32187ca46aa0ee234492b98ed0165b2c6 /timebase.c | |
| parent | 87d70dd17c13b7c5afa6d54c161e4f00ef4d514a (diff) | |
| download | gpsd-718f7af4f049cc44273f89e74fd3dab9510e7478.tar.gz | |
Add a warning by Andy Walls.
Diffstat (limited to 'timebase.c')
| -rw-r--r-- | timebase.c | 3 |
1 files changed, 2 insertions, 1 deletions
@@ -63,7 +63,8 @@ available. get the device to report it. The latter is not a given; SiRFs before firmware rev 2.3.2 don't report it unless special subframe data reporting is enabled, which requires 38400bps. Evermore GPSes can't be made to -report it at all. +report it at all. Furthermore, before the almanac load the GPS may report +a fixed (and possibly out of date) offset. Conclusion: if the system clock isn't accurate enough that we can deduce what rollover period we're in, we're utterly hosed. Furthermore, if it's |