diff options
author | Eric S. Raymond <esr@thyrsus.com> | 2016-08-26 10:28:45 -0400 |
---|---|---|
committer | Eric S. Raymond <esr@thyrsus.com> | 2016-08-26 10:28:45 -0400 |
commit | cf205eeb595d2b80947de481112fb1d42b10699d (patch) | |
tree | e1bcc0ecff24c1937b4dfb1450df629836ad0b68 /www | |
parent | d8eae2c73a707f215e2146568d5353329a25dcfa (diff) | |
download | gpsd-cf205eeb595d2b80947de481112fb1d42b10699d.tar.gz |
Documentation polishing.
Diffstat (limited to 'www')
-rw-r--r-- | www/gpsd-time-service-howto.txt | 11 | ||||
-rw-r--r-- | www/protocol-evolution.txt | 4 |
2 files changed, 10 insertions, 5 deletions
diff --git a/www/gpsd-time-service-howto.txt b/www/gpsd-time-service-howto.txt index 5783280f..414508dc 100644 --- a/www/gpsd-time-service-howto.txt +++ b/www/gpsd-time-service-howto.txt @@ -2,7 +2,7 @@ :description: How to set up an NTP Stratum 1 server using GPSD. :keywords: time, GPSD, NTP, time, precision, 1PPS, PPS, stratum, jitter Gary E. Miller <gem@rellim.com>, Eric S. Raymond <esr@thyrsus.com> -v2.8, July 2016 +v2.9, Aug 2016 This document is mastered in asciidoc format. If you are reading it in HTML, you can find the original at the GPSD project website. @@ -244,13 +244,13 @@ to the Carrier Detect pin on the USB adapter. (This is known as the With this design, 1PPS from the engine will turn into a USB event that becomes visible to the host system (and GPSD) the next time the USB -device is polled. USB 1.1 polls 1024 slots ever second. Each slot is +device is polled. USB 1.1 polls 1024 slots every second. Each slot is polled in the same order every second. When a device is added it is assigned to one of those 1024 polling slots. It should then be clear that the accuracy of a USB 1.1 connected GPS receiver would be about 1 mSec. -As of early 2015 no USB GPS receiver we know of implements the higher +As of mid-2016 no USB GPS receiver we know of implements the higher polling-rate options in USB 2 and 3 or the interrupt capability in USB 3. When one does, and if it has the Macx-1 mod, higher USB accuracy will ensue. @@ -1825,3 +1825,8 @@ by Jaap Winius <jwinius@rjsystems.nl>. 2.8 July 2016 Mention required version of gpsd Fix Typos. + +2.9 August 2016 + Fix typos. + +// end diff --git a/www/protocol-evolution.txt b/www/protocol-evolution.txt index 33655b31..c697b030 100644 --- a/www/protocol-evolution.txt +++ b/www/protocol-evolution.txt @@ -66,7 +66,7 @@ For some devices (not all) you could add E and get error estimates. Other data such as course and rate of climb/sink might be available via other single-letter commands. I say "might be" because in those early days gpsd didn't attempt to compute error estimates or velocities -if the GPS didn't explicitly supply them. I fixed that, later. but +if the GPS didn't explicitly supply them. I fixed that, later, but this essay is about protocol design so I'm going to ignore all the issues associated with the implementation for the rest of the discussion. @@ -534,7 +534,7 @@ GPSD-NG is an application of JSON. Not a completely pure one; the request identifiers, are, for convenience reasons, outside the JSON objects. But close enough. -In recent years, metaprotocols have become in important weapon in +In recent years, metaprotocols have become an important weapon in the application-protocol designer's toolkit. XML, and its progeny SOAP and XML-RPC, are the best known metaprotocols. YAML (of which JSON is essentially a subset) has a following as well. |