Commit 2bd5e39c authored by Eric S. Raymond's avatar Eric S. Raymond

Revision of GPS rollover warning.

parent 54d1dab3
Pipeline #7866852 passed with stage
in 5 minutes and 51 seconds
...@@ -264,11 +264,11 @@ link:refclock.html[Reference Clock Drivers] ...@@ -264,11 +264,11 @@ link:refclock.html[Reference Clock Drivers]
== Known bugs == == Known bugs ==
If your GPS has firmware made more than 1024 weeks (19 years and 36 If your GPS has firmware made more than 1024 weeks (19 years and 36
weeks) in the past, its internal date counter may well wrap around and weeks) in the past, its internal date counter will almost certainly
generate spurious timestamps. Beginning in January 2018, newer GPSes wrap around and generate spurious timestamps. Beginning in January
may have a longer wraparound (8192 weeks, or 157 years and 28 weeks) 2018, newer GPSes may have a longer wraparound (8192 weeks, or 157
but it is not safe to bet that any given receiver will have firmware years and 28 weeks) but it is not safe to bet that any given receiver
updated to take advantage of this. will have firmware updated to take advantage of this.
This problem is fundamental and cannot be compensated for in code This problem is fundamental and cannot be compensated for in code
without relying on the accuracy of the local system clock, which without relying on the accuracy of the local system clock, which
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment