summaryrefslogtreecommitdiff
path: root/INSTALL
diff options
context:
space:
mode:
authorEric S. Raymond <esr@thyrsus.com>2004-09-28 18:43:32 +0000
committerEric S. Raymond <esr@thyrsus.com>2004-09-28 18:43:32 +0000
commit4fa434843ab45684363b4c3f945c9e00fe634098 (patch)
tree83a4d4317f7398cc64888b08842b956ac6b9b613 /INSTALL
parentd3ff6e618a626a1f522094e8764c7748d486c5cc (diff)
downloadgpsd-4fa434843ab45684363b4c3f945c9e00fe634098.tar.gz
How to report working hardware.
Diffstat (limited to 'INSTALL')
-rw-r--r--INSTALL27
1 files changed, 25 insertions, 2 deletions
diff --git a/INSTALL b/INSTALL
index ae300b5e..8fd6a869 100644
--- a/INSTALL
+++ b/INSTALL
@@ -57,6 +57,29 @@ thing. You should see a GUI panel with position/velocity-time information,
and a satellite display. The displays won't look very interesting until
the GPS acquires satellite lock.
-
-
+7. Check out the list of supported hardware at
+
+ http://gpsd.berlios.de/hardware.html
+
+If your GPS isn't on the list, please send us information to add a new
+line to the table. Here's what we need:
+
+1. Name (preferably with a URL to the vendor's product page or spec sheet).
+2. Chipset. Ideally we'd like to know both the GPS engine chip and
+ the USB-to-serial chip the device uses. 80% of the time this will be
+ SiRF-II + PL2303, but it's the exceptions that are interesting.
+3. Interface type -- RS232, USB, CF, etc.
+4. Vendor (preferably with a URL to the vendor's website).
+5. gpsd type -- usually this will be 'n'. If you had to specify a
+ non-NMEA driver type to make gpsd work, give it.
+6. Version of gpsd you tested with.
+7. NMEA protocol version.
+8. List of NMEA sentences the GPS emits.
+9. Notes -- anything interesting or unusual about this GPS.
+
+You may get some help on fields 2, 7, and 8 by running gpsprobe. Note that
+you will have to stop gpsd to do this.
+
+We can also use updates of the latest version number known to work with
+hardware already supported.