summaryrefslogtreecommitdiff
path: root/www/writing-a-driver.xml
diff options
context:
space:
mode:
authorEric S. Raymond <esr@thyrsus.com>2013-10-30 12:32:12 -0400
committerEric S. Raymond <esr@thyrsus.com>2013-10-30 12:39:26 -0400
commitd9b8758935f902fb0ea77fee09e9627e09462a11 (patch)
treed6dbb060ce2162abe50b6dcada9b23c0a80ad63d /www/writing-a-driver.xml
parent7a5a25946be3db4bd8c08d1a5b126f43131144eb (diff)
downloadgpsd-d9b8758935f902fb0ea77fee09e9627e09462a11.tar.gz
Separate ntpd support from chrony support, step 1.
ntp_offset becomes time_offset. There is a new config symbol CHRONY_ENABLE; most time service code is npw controlled by TIMESERVICE_ENABLE. The file ntpshm.c becomes timeexport.c This change is not complete. More disentanglement has to be done inside timeexport.c itself; at the moment enabling one but not both of ntpshm or chrony will probably break its compile. The point of getting this commit out is so Gary will see the new baseline code ASAP. All regression tests pass.
Diffstat (limited to 'www/writing-a-driver.xml')
-rw-r--r--www/writing-a-driver.xml19
1 files changed, 14 insertions, 5 deletions
diff --git a/www/writing-a-driver.xml b/www/writing-a-driver.xml
index ab624354..1145fcfa 100644
--- a/www/writing-a-driver.xml
+++ b/www/writing-a-driver.xml
@@ -15,6 +15,14 @@
<revhistory>
<revision>
+ <revnumber>1.12</revnumber>
+ <date>30 Oct 2013</date>
+ <authorinitials>er</authorinitials>
+ <revremark>
+ Updated by esr; ntp_offset becomes time_offset
+ </revremark>
+ </revision>
+ <revision>
<revnumber>1.11</revnumber>
<date>19 Jan 2011</date>
<authorinitials>er</authorinitials>
@@ -745,11 +753,12 @@ possible, assemble your packet in
gpsmon to display the control messages it sends for you.</para>
<!-- added by ESR, 2009 -->
-<para><structfield>.ntp_offset</structfield> points to code to compute
-an offset to be added, additionally to that in
-<filename>ntp.conf</filename> (if any) when shipping time notifications
-to NTP. If multiple sentences set TIME_IS, this will differ by
-sentence type; it should differ by baud rare, as well. </para>
+<para><structfield>.timr_offset</structfield> points to code to
+compute an offset to be added, additionally to that in
+<filename>ntp.conf</filename> (if any) when shipping time
+notifications to NTP, or the equivalent configuration file for
+chrony. If multiple sentences set TIME_IS, this will differ by
+sentence type; it should differ by baud rate, as well. </para>
</sect1>