diff options
| -rw-r--r-- | gpsd.8 | 12 | ||||
| -rw-r--r-- | gpsd.xml | 20 | ||||
| -rw-r--r-- | www/hacking.html | 12 | ||||
| -rw-r--r-- | www/index.html.in | 12 |
4 files changed, 31 insertions, 25 deletions
@@ -2,7 +2,7 @@ .\" It was generated using the DocBook XSL Stylesheets (version 1.69.1). .\" Instead of manually editing it, you probably should edit the DocBook XML .\" source for it and then use the DocBook XSL Stylesheets to regenerate it. -.TH "GPSD" "8" "09/24/2006" "9 Aug 2004" "9 Aug 2004" +.TH "GPSD" "8" "10/29/2006" "9 Aug 2004" "9 Aug 2004" .\" disable hyphenation .nh .\" disable justification (adjust text to left margin only) @@ -288,7 +288,7 @@ The recommended mode for clients is watcher mode. In watcher mode gpsd ships a line of data to the client each time the GPS gets either a fix update or a satellite picture, but rather than being raw NMEA the line is a gpsd 'o' or 'y' response. Additionally, watching clients get notifications in the form X=0 or X=%f when the online/offline status of the GPS changes. .PP -Clients should be prepared for the possibility that additional fields (such as heading or roll/pitch/yaw) may be added to the O command, and not treat the occurrence of extra fields as an error. The protocol number will be incremented if and when sych fields are added. +Clients should be prepared for the possibility that additional fields (such as heading or roll/pitch/yaw) may be added to the O command, and not treat the occurrence of extra fields as an error. The protocol number will be incremented if and when such fields are added. .PP Sending SIGHUP to a running gpsd @@ -465,7 +465,9 @@ have made a point of not looking at it. The links to several documents that collect publicly disclosed information about the protocol. .PP gpsd -parses the following NMEA sentences: RMC, GGA, GSA, GSV, ZDA. It recognizes these with either the normal GP talker\-ID prefix, or with the II prefix emitted by Seahawk Autohelm marine navigation systems, or with the IN prefix emitted by some Garmin units. It recognizes one vendor extension, PGRME. Note that +parses the following NMEA sentences: RMC, GGA, GLL, GSA, GSV, VTG, ZDA. It recognizes these with either the normal GP talker\-ID prefix, or with the II prefix emitted by Seahawk Autohelm marine navigation systems, or with the IN prefix emitted by some Garmin units. It recognizes one vendor extension, the PGRME emitted by some Garmin GPS models. +.PP +Note that gpsd returns pure decimal degrees, not the hybrid degree/minute format described in the NMEA standard. .SH "SEE ALSO" @@ -478,8 +480,8 @@ returns pure decimal degrees, not the hybrid degree/minute format described in t \fBrtcm\-104\fR(5). .SH "AUTHORS" .PP -Remco Treffcorn, Derrick Brashear, Russ Nelson, Eric S. Raymond. This manual page by Eric S. Raymond -<esr@thyrsus.com>. There is a project page +Remco Treffcorn, Derrick Brashear, Russ Nelson, Eric S. Raymond, Chris Kuethe. This manual page by Eric S. Raymond +<esr@thyrsus.com>. There is a project site at [2]\&\fIhere\fR. .SH "REFERENCES" .TP 3 @@ -659,7 +659,7 @@ changes.</para> <para>Clients should be prepared for the possibility that additional fields (such as heading or roll/pitch/yaw) may be added to the O command, and not treat the occurrence of extra fields as an error. -The protocol number will be incremented if and when sych fields +The protocol number will be incremented if and when such fields are added.</para> <para>Sending SIGHUP to a running <application>gpsd</application> @@ -962,11 +962,13 @@ website</ulink> links to several documents that collect publicly disclosed information about the protocol.</para> <para><application>gpsd</application> parses the following NMEA -sentences: RMC, GGA, GSA, GSV, ZDA. It recognizes these with -either the normal GP talker-ID prefix, or with the II prefix emitted -by Seahawk Autohelm marine navigation systems, or with the IN prefix -emitted by some Garmin units. It recognizes one vendor extension, -PGRME. Note that <application>gpsd</application> returns pure decimal +sentences: RMC, GGA, GLL, GSA, GSV, VTG, ZDA. It recognizes these +with either the normal GP talker-ID prefix, or with the II prefix +emitted by Seahawk Autohelm marine navigation systems, or with the IN +prefix emitted by some Garmin units. It recognizes one vendor +extension, the PGRME emitted by some Garmin GPS models.</para> + +<para>Note that <application>gpsd</application> returns pure decimal degrees, not the hybrid degree/minute format described in the NMEA standard.</para> @@ -984,9 +986,9 @@ standard.</para> <refsect1 id='maintainer'><title>AUTHORS</title> -<para>Remco Treffcorn, Derrick Brashear, Russ Nelson, Eric S. Raymond. -This manual page by Eric S. Raymond <email>esr@thyrsus.com</email>. -There is a project page <ulink +<para>Remco Treffcorn, Derrick Brashear, Russ Nelson, Eric S. Raymond, +Chris Kuethe. This manual page by Eric S. Raymond +<email>esr@thyrsus.com</email>. There is a project site at <ulink url="http://gpsd.berlios.de/">here</ulink>.</para> </refsect1> diff --git a/www/hacking.html b/www/hacking.html index 9bdcf9ad..13b4d140 100644 --- a/www/hacking.html +++ b/www/hacking.html @@ -99,7 +99,7 @@ source distribution.</p> <li><a href="#designahead">Designing Ahead</a></li> <ol> <li><a href="#nonpvt">Non-PVT Data</a></li> -<li><a href="#protov4">Design Sketch for Version 4 Protocol</a></li> +<li><a href="#protov4">Design Sketch for GPSD-NG, the Next-Generation GPSD Protocol</a></li> </ol> <li><a href="#blindalleys">Blind alleys</a></li> <ol> @@ -1162,15 +1162,17 @@ type as revealed by I, how to interpret and label the data in the private-use fields.</p> <p>If we go for alternative (2), the first consequence is that we -actually have to implement a Version 4 protocol. The existing GPSD +actually have to implement a next-generation protocol. The existing GPSD protocol is about out of namespace.</p> -<h2 id="protov4">Design Sketch for Version 4 Protocol</h2> +<h2 id="protov4">Design Sketch for GPSD-NG, the Next-Generation GPSD Protocol</h2> <p>There are almost no more letters left in the namespace of the GPSD version 3 protocol. At time of writing in late 2006 we can have one -more command, 'h', and that's it. After that, extending the set -will require a new command/response syntax.</p> +more command, 'h', and that's it. After that, extending the set will +require a new command/response syntax. Some posts in thew dev-list +arcvhive refer to this as "Version 4", but that is a rev level we may +or may not reach before GPSD-NG has to be implemented.</p> <p>Steps towards defining a new syntax have been taken. The senior developers have agreed on a new protocol with a basic sentence syntax diff --git a/www/index.html.in b/www/index.html.in index a08ce6f2..35599bd8 100644 --- a/www/index.html.in +++ b/www/index.html.in @@ -73,12 +73,12 @@ href="http://qpegps.sourceforge.net/">gpeGPS</a>, <a href="http://www.gnustep.it/enrico/position/">position</a> and <a href="http://roadmap.digitalomaha.net/index.html">roadmap</a>.</p> -<p>Under Linux, gpsd normally runs with zero configuration. The RPM -installs hotplug scripts that do the right thing when a USB device -goes active, launching <code>gpsd</code> if needed and telling -<code>gpsd</code> which device to read data from. Then, -<code>gpsd</code> deduces a baud rate and GPS type by looking at the -data stream.</p> +<p>Under Linux,<code>gpsd</code> normally runs with zero +configuration. The RPM installs hotplug scripts that do the right +thing when a USB device goes active, launching <code>gpsd</code> if +needed and telling <code>gpsd</code> which device to read data from. +Then, <code>gpsd</code> deduces a baud rate and GPS type by looking at +the data stream.</p> <p><code>gpsd</code> is high-quality, carefully-audited code. It is regularly checked with the standard mode of <a href='http://www.splint.org'>splint</a>, |