diff options
| author | Eric S. Raymond <esr@thyrsus.com> | 2011-10-04 13:57:34 -0400 |
|---|---|---|
| committer | Eric S. Raymond <esr@thyrsus.com> | 2011-10-04 13:57:34 -0400 |
| commit | 248c24de6729332e394b626b1930d1d52047d6af (patch) | |
| tree | ebb329b9d633691acff6ff4616780127bcddc05f /www | |
| parent | 71dd3369e36e1e39bf578e37a6c3297d42156c7a (diff) | |
| download | gpsd-248c24de6729332e394b626b1930d1d52047d6af.tar.gz | |
More website cleanup.
Except for bgcolor, width, and border attributes, all pages that claim
to be validated actually are valid (again).
Diffstat (limited to 'www')
| -rw-r--r-- | www/faq.html.in | 77 | ||||
| -rw-r--r-- | www/hardware-head.html.in | 124 | ||||
| -rw-r--r-- | www/hardware-tail.html | 11 |
3 files changed, 109 insertions, 103 deletions
diff --git a/www/faq.html.in b/www/faq.html.in index 39c550b7..2984afa6 100644 --- a/www/faq.html.in +++ b/www/faq.html.in @@ -1,11 +1,12 @@ -<!doctype html public "-//w3c//dtd html 4.0 transitional//en"> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" + "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"> <!-- @MASTER@ --> -<html> <head> - <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> - <meta name="Author" content="Eric S. Raymond"> - <meta name="Description" content="GPSD Frequently Asked Questions"> - <meta name="Keywords" content="GPS, translator, GIS"> + <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> + <meta name="Author" content="Eric S. Raymond" /> + <meta name="Description" content="GPSD Frequently Asked Questions" /> + <meta name="Keywords" content="GPS, translator, GIS" /> <link rel="stylesheet" href="main.css" type="text/css"/> <title>GPSD FAQ</title> </head> @@ -67,26 +68,26 @@ GPSD Frequently Asked Questions <div id="Content"> <ul> -<li><a href='#verify'>How can I verify operation of a new GPS?</a><br/> -<li><a href='#bug-reporting'>How do I report bugs in GPSD?</a><br/> -<li><a href='#startup'>Why does getting a fix take so long after powerup?</li> +<li><a href='#verify'>How can I verify operation of a new GPS?</a></li> +<li><a href='#bug-reporting'>How do I report bugs in GPSD?</a></li> +<li><a href='#startup'>Why does getting a fix take so long after powerup?</a></li> <li><a href='#timelag'>Why does GPS time lag wall time by 11-15 seconds?</a></li> -<li><a href='#speed'>Why does my receiver report wildly fluctuating speed?</a><br/> -<li><a href='#gpsdrive'>Why do I get implausibly low speeds when using gpsdrive?</a><br/> -<li><a href='#kismet'>Why do I get no results when I try to use <code>gpsd</code> with Kismet?</a><br/> -<li><a href='#bluetooth'>Why do I have to restart <code>gpsd</code> whenever I power-cycle my Bluetooth device?</a><br/> -<li><a href='#lockup'>My <code>gpsd</code> sometimes stops responding overnight</a><br/> -<li><a href='#why_not_parse_nmea'>Why use the <code>gpsd</code> protocol rather than parsing raw NMEA?</a><br/> -<li><a href='#interfacing'>How should I interface my application with <code>gpsd</code>?</a><br/> -<li><a href='#agps'>Can GPSD use Assisted GPS data from cellphone networks?</code>?</a><br/> -<li><a href='#accuracy'>How can I improve fix accuracy from my GPS?</a><br/> -<li><a href='#time'>How can I improve time reference accuracy from my GPS?</a><br/> -<li><a href='#sleep'>Why does my GPS get lost when I sleep/wake my laptop?</a><br/> -<li><a href='#baud'>Why is there no option to fix baud rate?</a><br/> -<li><a href='#willitwork'>Will this GPS work? It's not on the hardware list.</a> -<li><a href='#nmea2000'>Does gpsd support NMEA2000?.</a><br/> -<li><a href='#conflict'>Why does GPSD interfere with non-GPS USB devices?</a></br> -<li><a href='#efficiency'>What is gpsd's CPU and power overhead?</a></br> +<li><a href='#speed'>Why does my receiver report wildly fluctuating speed?</a></li> +<li><a href='#gpsdrive'>Why do I get implausibly low speeds when using gpsdrive?</a></li> +<li><a href='#kismet'>Why do I get no results when I try to use <code>gpsd</code> with Kismet?</a></li> +<li><a href='#bluetooth'>Why do I have to restart <code>gpsd</code> whenever I power-cycle my Bluetooth device?</a></li> +<li><a href='#lockup'>My <code>gpsd</code> sometimes stops responding overnight</a></li> +<li><a href='#why_not_parse_nmea'>Why use the <code>gpsd</code> protocol rather than parsing raw NMEA?</a></li> +<li><a href='#interfacing'>How should I interface my application with <code>gpsd</code>?</a></li> +<li><a href='#agps'>Can GPSD use Assisted GPS data from cellphone networks?</a></li> +<li><a href='#accuracy'>How can I improve fix accuracy from my GPS?</a></li> +<li><a href='#time'>How can I improve time reference accuracy from my GPS?</a></li> +<li><a href='#sleep'>Why does my GPS get lost when I sleep/wake my laptop?</a></li> +<li><a href='#baud'>Why is there no option to fix baud rate?</a></li> +<li><a href='#willitwork'>Will this GPS work? It's not on the hardware list.</a></li> +<li><a href='#nmea2000'>Does gpsd support NMEA2000?.</a></li> +<li><a href='#conflict'>Why does GPSD interfere with non-GPS USB devices?</a></li> +<li><a href='#efficiency'>What is gpsd's CPU and power overhead?</a></li> </ul> <h1 id='verify'>How can I verify operation of a new GPS?</h1> @@ -215,7 +216,7 @@ all, is the firmware version. You will want that for your report.</p> <h3 id="logformat">8. Annotate the capture log and send us a copy</h3> <p>We'll describe the annotation steps here for completeness, but the -easiest way to do this is with <a href="@WEBFORM">our web form</a> +easiest way to do this is with <a href="@WEBFORM">our web form</a>.</p> <p>A logfile should consist of an identifying header followed by a straight unencoded dump of receiver data, whether NMEA or binary. The @@ -225,8 +226,8 @@ Here is the beginning of one log file I already have:</p> <pre> # Name: Magellan eXplorist 210 # Chipset: unknown -# Submitted-by: "Paul B van den Berg" <paulberg@wanadoo.nl> -# Date: 20 May 2006 +# Submitted-by: "Paul B van den Berg" <paulberg@wanadoo.nl> +# Date: 2006-05-26 # Location: Groningen, NL, 53.2N 6.6E # # mode V2.1 GSA @@ -608,7 +609,7 @@ modern kernels. Both USB and RS232 will incur that approximately USB serial devices. In a default Linux configuration, USB serial device name do not depend on which physical port you plug the USB/serial adaptor, but on what order you plug devices in: 1st device -gets /dev/ttyUSB0, 2nd gets /dev/ttyUSB1, etc.... +gets /dev/ttyUSB0, 2nd gets /dev/ttyUSB1, etc....</p> <p>This collides with what happens during a suspend/resume. If you suspends while <code>gpsd</code> has a device active, it will hold the @@ -623,7 +624,7 @@ that is actually a symlink which gets modified by hotplug events, and give <code>gpsd</code> that device when you invoke it. You'll need <a href="70-persistent-usb-gps.rules">these replacement udev rules</a>, and the experience required to patch them so the vendor ID in the last -one matches your GPS hardware (look in your lsusb output). +one matches your GPS hardware (look in your lsusb output).</p> <h1 id='web'>How do I get gpsd data into a web page?</h1> @@ -636,7 +637,7 @@ instructions.</p> <p>Another way is to use a perl CGI script that leverages Net::GPSD like this...</p> -<code><pre> +<pre><code> #!/usr/bin/perl -w use strict; use Net::GPSD; @@ -661,11 +662,11 @@ srsName="urn:ogc:def:crs:EPSG:6.6:4326"> </Report> }; </code> -</pre></code> +</code></pre> <p>This will return something like:</p> -<code><pre> +<pre><code> <?xml version='1.0'?> <Report xmlns:gml="http://www.opengis.net/gml"> <items> @@ -679,7 +680,7 @@ srsName="urn:ogc:def:crs:EPSG:6.6:4326"> </Item> </items> </Report> -</pre></code> +</code></pre> <h1 id='baud'>Why is there no option to fix baud rate?</h1> @@ -705,10 +706,10 @@ the bit rate just before starting gpsd. For example, suppose you know that your GPS is on serial port 0 and operates at a fixed bps of 54600. You can set that up like this:</p> -<code><pre> +<pre><code> stty speed 54600 </dev/ttyS0 gpsd -nN /dev/ttyS0 -</pre></code> +</code></pre> <h1 id='willitwork'>Will this GPS work? It's not on the hardware list.</h1> @@ -775,7 +776,7 @@ one is not already running) and puts a copy of the device path in an internal stash list. Later, if a client application requests GPS data, <code>gpsd</code> will try to read from the device, and discard it from the stash list if it is not emitting data that <code>gpsd</code> -recognizes.<p> +recognizes.</p> <p>GPSD's notion of "might be a GPS" depends on the fact that all USB GPSes are made with one of a small number of USB-to-serial adapter @@ -815,6 +816,6 @@ at steadily less than 1% on a low-power, low-speed ARM SBC.</p> </div> <hr/> -<script language="JavaScript" src="datestamp.js" type='text/javascript'></script> +<script src="datestamp.js" type='text/javascript'></script> </body> </html> diff --git a/www/hardware-head.html.in b/www/hardware-head.html.in index f49f3546..e689e588 100644 --- a/www/hardware-head.html.in +++ b/www/hardware-head.html.in @@ -1,14 +1,15 @@ -<!doctype html public "-//w3c//dtd html 4.0 transitional//en"> -<html> +<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" + "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> +<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"> <head> - <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> - <meta name="Author" content="Eric Raymond"> - <meta name="Description" content="Hardware known to work with GPSD."> - <meta name="Keywords" content="GPS, translator, mxmap, GIS"> + <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/> + <meta name="Author" content="Eric Raymond"/> + <meta name="Description" content="Hardware known to work with GPSD."/> + <meta name="Keywords" content="GPS, translator, mxmap, GIS"/> <title>Compatible GPSes</title> <link rel="stylesheet" href="main.css" type="text/css"/> </head> - +<body> <div id="Header">Compatible Hardware</div> <div id="Menu"> @@ -22,7 +23,7 @@ <a href="xgps-sample.html">Screenshots</a><br/> <a href="index.html#recipes">Recipes</a><br/> <a href="index.html#others">Other GPSDs</a><br/> - Hardware</a><br/> + Hardware<br/> <a href="for-vendors.html">For GPS Vendors</a><br/> <a href="wishlist.html">Wish List</a><br/> <a href="hall-of-shame.html">Hall of Shame</a><br/> @@ -67,29 +68,29 @@ <span>Search for hardware information here:</span> <!-- SiteSearch Google --> -<form method="get" action="http://www.google.com/custom" target="_top"> -<table border="0" bgcolor="#ffffff"> -<tr><td nowrap="nowrap" valign="top" align="left" height="32"> +<form method="get" action="http://www.google.com/custom"> +<table border="0"> +<tr><td valign="top" align="left"> <a href="http://www.google.com/"> -<img src="http://www.google.com/logos/Logo_25wht.gif" border="0" alt="Google" align="middle"></img></a> +<img src="http://www.google.com/logos/Logo_25wht.gif" border="0" alt="Google"></img></a> </td> -<td nowrap="nowrap"> +<td> <input type="hidden" name="domains" value="@SITESEARCH@"></input> <input type="text" name="q" size="31" maxlength="255" value=""></input> <input type="submit" name="sa" value="Search"></input> </td></tr> <tr> <td> </td> -<td nowrap="nowrap"> +<td> <table> <tr> <td> <input type="radio" name="sitesearch" value=""></input> -<font size="-1" color="#000000">Web</font> +Web </td> <td> <input type="radio" name="sitesearch" value="@SITESEARCH@" checked="checked"></input> -<font size="-1" color="#000000">@SITESEARCH@</font> +@SITESEARCH@ </td> </tr> </table> @@ -111,10 +112,11 @@ RS232C or USB interface that advertises NMEA-0183 compliance. Here are some notes on hardware we have tested. Hyperlinks lead to technical information. The "Works with" column is the last -<code>gpsd</code> version with which this receiver is known to have been -successfully tested; A <img src="regression.png"/> in this column -means we have a regression test load for the device that is checked -before each release. Vendors are listed in alphabetical order.</p> +<code>gpsd</code> version with which this receiver is known to have +been successfully tested; A <img src="regression.png" alt="Regression +icon"/> in this column means we have a regression test load for the +device that is checked before each release. Vendors are listed in +alphabetical order.</p> <p>There is also a <a href="#timing">table of PPS-capable receivers</a> which may be appropriate for timing use.</p> @@ -125,55 +127,59 @@ These bugs may send affected GPSes catatonic. See this <a href="upstream-bugs.html#bluetooth">bug warning</a> for a description of the problem. Where possible, we indicate this in the device table.</p> -<p>Icons used in the table: +<p>Icons used in the table:</p> <ul> -<li><img src="star.png"/><img src="star.png"/><img src="star.png"/><img -src="star.png"> marks devices with <b>Excellent</b> performance: gpsd +<li><img src="star.png" alt="Star icon"/><img src="star.png" alt="Star +icon"/><img src="star.png" alt="Star icon"/><img src="star.png" +alt="Star icon"/> marks devices with <b>Excellent</b> performance: gpsd recognizes the receiver rapidly and reliably, reports are complete and correct.</li> -<li><img src="star.png"/><img src="star.png"/><img src="star.png"/> marks -devices with <b>Good</b> performance: <tt>gpsd</tt> has minor problems -or lag recognizing the device, but reports are complete and -correct.</li> +<li><img src="star.png" alt="Star icon"/><img src="star.png" alt="Star +icon"/><img src="star.png" alt="Star icon"/> marks devices with +<b>Good</b> performance: <tt>gpsd</tt> has minor problems or lag +recognizing the device, but reports are complete and correct.</li> -<li><img src="star.png"/><img src="star.png"/> marks devices with -<b>Fair</b> performance: reports have minor dropouts or problems, -including occasional transient nonsense values.</li> +<li><img src="star.png" alt="Star icon"/><img src="star.png" alt="Star +icon"/> marks devices with <b>Fair</b> performance: reports have minor +dropouts or problems, including occasional transient nonsense +values.</li> -<li><img src="star.png"/> marks devices with <b>Poor</b> performance: -reports frequently have values that are wrong or nonsense.</li> +<li><img src="star.png" alt="Star icon"/> marks devices with +<b>Poor</b> performance: reports frequently have values that are wrong +or nonsense.</li> -<li><img src="bomb.png"/> marks devices which are <b>Broken</b>; +<li><img src="bomb.png" alt="Bomb icon"/> marks devices which are <b>Broken</b>; gpsd frequently fails to recognize the device at all.</li> -<li><img src="noconfigure.png"/> marks devices that needed the -<tt>gpsd -b</tt> option when tested. Usually these are Bluetooth -devices with defective firmware that does not handle baud-rate changes -properly. Some poorly-designed USB devices choke if they are fed too -many probe strings; these may work better with recent versions of -<tt>gpsd</tt>, which interleaves probe writes with the first few -packet reads.</li> - -<li><img src="regression.png"/> marks devices for which we have a -regression-test load. These are checked on every release.</li> - -<li><img src="discontinued.png"/> marks devices that have been -discontinued by their manufacturers.</li> - -<li><img src="hotplug.png"/> marks devices which will be recognized by -the Linux hotplug system when they are plugged in. If you installed -<tt>gpsd</tt> from a binary package,or did "make udev-install" from -the source distribution, this should mean you never have to launch -<tt>gpsd</tt> manually; the udev syatem will launch it for you when -it sees a device of this kind go active.</li> -</ul></p> - -<p>Note that in most cases (including the <img src="noconfigure.png"/> -bug), poor ratings reflect problems not in <tt>gpsd</tt> but rather in -device design and firmware so badly botched that <tt>gpsd</tt> cannot -compensate.</p> +<li><img src="noconfigure.png" alt="No-configure icon"/> marks devices +that needed the <code>gpsd -b</code> option when tested. Usually these are +Bluetooth devices with defective firmware that does not handle +baud-rate changes properly. Some poorly-designed USB devices choke if +they are fed too many probe strings; these may work better with recent +versions of <code>gpsd</code>, which interleaves probe writes with the +first few packet reads.</li> + +<li><img src="regression.png" alt="Regression-test icon"/> marks +devices for which we have a regression-test load. These are checked on +every release.</li> + +<li><img src="discontinued.png" alt="Discontinued icon"/> marks +devices that have been discontinued by their manufacturers.</li> + +<li><img src="hotplug.png" alt="Hotplug icon"/> marks devices which +will be recognized by the Linux hotplug system when they are plugged +in. If you installed <code>gpsd</code> from a binary package,or did "make +udev-install" from the source distribution, this should mean you never +have to launch <code>gpsd</code> manually; the udev syatem will launch it +for you when it sees a device of this kind go active.</li> +</ul> + +<p>Note that in most cases (including the <img src="noconfigure.png" +alt="No-configure icon"/> bug), poor ratings reflect problems not in +<code>gpsd</code> but rather in device design and firmware so badly +botched that <code>gpsd</code> cannot compensate.</p> <p>This table is generated from a capability database in the <code>gpsd</code> source tree. Please help us enrich the database with diff --git a/www/hardware-tail.html b/www/hardware-tail.html index dbada9ef..955b7ef0 100644 --- a/www/hardware-tail.html +++ b/www/hardware-tail.html @@ -1,6 +1,6 @@ <!-- hardware-tail.html begins here --> -<a name="timing"></a> +<a id="timing"></a> <h2>PPS and GPSD:</h2> <p>Many GPS receivers offer a 1PPS (one pulse per second) output that @@ -123,7 +123,7 @@ serial data accurate to about 250mS.</p> <td>Garmin GPS18/LVC</td> <td align="center">1usec</td> <td align="center">0.125sec</td> -<td align="center">Must be outside with a clear sky view.<br>At 19200bps; drops to 0.525 at 4800bps</td> +<td align="center">Must be outside with a clear sky view.<br/>At 19200bps; drops to 0.525 at 4800bps</td> </tr> <tr> <td>Rockwell Jupiter</td> @@ -138,7 +138,7 @@ serial data accurate to about 250mS.</p> <td align="center">-</td> </tr> <tr> -<td>SiRFstar3<br>(GlobalSat MR-350P)</td> +<td>SiRFstar3<br/>(GlobalSat MR-350P)</td> <td align="center">1usec</td> <td align="center">-</td> <td align="center">May work inside wood frame buildings.</td> @@ -151,7 +151,7 @@ serial data accurate to about 250mS.</p> </tr> </table> -<a name="raw"></a> +<a id="raw"></a> <h2>Raw Measurements and GPSD:</h2> <p>All gpses require "raw" measurements internally to compute a navigation @@ -177,7 +177,6 @@ serial data accurate to about 250mS.</p> <td>sirfstar1 has raw data in message 5, sirfstar2 has raw data in message 28, sirfstar3 has some raw data in message 28 but carrier phase is not available. rumor has it that carrier phase is available as a premium feature in superstar3.</td> </tr> <tr> -<tr> <td>ublox</td> <td align="center">Partial</td> <td>The RXM-RAW message contains raw data. This is implemented in all Antaris chips. This is only implemented in the timing versions of Antaris4. In ublox5 it is "only available with premium feature raw data". @@ -208,6 +207,6 @@ serial data accurate to about 250mS.</p> </div> <hr/> -<script language="JavaScript" src="datestamp.js" type='text/javascript'></script> +<script src="datestamp.js" type='text/javascript'></script> </body> </html> |