summaryrefslogtreecommitdiff
path: root/INSTALL
diff options
context:
space:
mode:
authorEric S. Raymond <esr@thyrsus.com>2011-09-17 19:26:28 -0400
committerEric S. Raymond <esr@thyrsus.com>2011-09-17 19:26:28 -0400
commit4fc47f0c9f25834363c2a5043ce6141ca5b971b2 (patch)
tree507234ff7a5cd8ff875b533dba114c0e1c79cd22 /INSTALL
parente38de2f8908fc56ba190f3396f1ba0f8ddb8757c (diff)
downloadgpsd-4fc47f0c9f25834363c2a5043ce6141ca5b971b2.tar.gz
Slight revision of some advice.
Diffstat (limited to 'INSTALL')
-rw-r--r--INSTALL22
1 files changed, 11 insertions, 11 deletions
diff --git a/INSTALL b/INSTALL
index 46055400..40cae3e0 100644
--- a/INSTALL
+++ b/INSTALL
@@ -63,24 +63,24 @@ relating to implicit_links in the scons recipe; you probably need to
build with implicit_links=no. And report your platform, ideally along
with a way of identifying it from Python, to the gpsd maintainers.
-For mice using an RS-232 port (which is no longer common) you will need
-serial-port support compiled into your kernel. Various USB-to-serial
-adapter chips found in GPSes require specific drivers. Under a stock
-Linux kernel these will load on demand whren the USB system sees the
-appropriate vendor/product ID combinations. If you are custom-building
-a Linux kernel for embedded deployment, you will need some subset of
-the following modules:
+For GPSes using an RS-232 port (which is no longer common) you will
+need serial-port support compiled into your kernel. Various
+USB-to-serial adapter chips found in GPSes require specific
+drivers. Under a stock Linux kernel these will load on demand whren
+the USB system sees the appropriate vendor/product ID combinations.
+If you are custom-building a Linux kernel for embedded deployment, you
+will need some subset of the following modules:
pl2303 Prolific Technology, Inc. PL2303 Serial Port
ftdi_sio FTDI 8U232AM / FT232
cypress_m8 M8/CY7C64013
cp210x Cygnal Integrated Products devices
garmin_gps Garmin USB mice including GPS-18
-cdc_am USB Communication Device Class Abstract Control Model interface
+cdc_am USB Communication Device Class Abstract Control Model interface
-These are listed in rough order of devices covered; the PL23203 by itself
-accounts for over 70% of deployed USB mice. We recommend building with
-pl2303, ftdi_sio, cypress_m8, and cp210x.
+These are listed in rough order of devices covered as of 2011; the
+PL23203 by itself accounts for over 70% of deployed USB mice. We
+recommend building with pl2303, ftdi_sio, cypress_m8, and cp210x.
For building from the source tree, or if you change the man page
source, xslt and docbook xsl style files are used to generate nroff