Merge branch 'master' of git.sv.gnu.org:/srv/git/gpsd

Conflicts:
	gpscap.ini

1 files changed, 226 insertions, 170 deletions

diff --git a/gpscap.ini b/gpscap.ini
index acbbbd64..4203d9a3 100644
--- a/gpscap.ini
+++ b/gpscap.ini
@@ -19,7 +19,7 @@
 # eval_unit    = Which GPSD devs have one for testing (list)
 # engine       = GPS chipset (may reference another section)
 # subtype      = engine subtype or firmware revision level
-# interfaces   = interface types: USB, RS-232, Bluetooth, CF, TTL, CAN. 
+# interfaces   = interface types: USB, RS-232, Bluetooth, CF, TTL, CAN.
 #                May be a list.
 # usbchip      = USB I/O chipset
 # pps	       = supports pulse-per-second precision time reporting
@@ -62,7 +62,7 @@
 #   "OEM module" is an un-cased circuit board with edge connectors; a
 #   "chipset" is what it sounds like.
 #   A "handset" is a standalone GPS with a display and human-usable
-#   controls. A "handsfree" is a hands-free unit with display designed for 
+#   controls. A "handsfree" is a hands-free unit with display designed for
 #   mounting on a car windshield or boat dash.
 # * In the rating field:
 #    "excellent" - gpsd recognizes the GPS rapidly and reliably,
@@ -76,95 +76,9 @@
 #    "other -- See Technical Notes.
 
 #
-# Chipsets
+# Chipsets (alphabetical)
 #
 
-[GenericSiRF]
-type = engine
-description = Capabilities generic to all SiRF chips
-# Sets 4800 baud shipping GGA+GSA+GSV+RMC
-to_nmea = 0xa0a200188102010100000101050101010000000100010001000112c00000b0b3
-to_native = $PSRF100,0,%b,8,1,0	# Sets 8N1 with specified speed
-
-[SiRF-1]
-type = engine
-description = Version 1 of the SiRF GPS engine
-engine = SiRF-1
-nmea = 2.2
-uses = GenericSiRF
-tested = 2.34
-rating = good
-logs = ublox-sirf1.log
-notes = ublox-sirf1.log was made from a device with ublox firmware and 
-      may not be typical of SiRF-1 chips.
-
-[SiRF-2]
-type = engine
-description = Version 2 of the SiRF GPS engine
-engine = SiRF-2
-# Later versions may do 2.3
-nmea = 2.2
-uses = GenericSiRF
-tested = 2.37
-rating = good
-logs = bu303b-nofix.log, bu303-climbing.log, bu303-moving.log, 
-     bu303-nofix.log, bu303-stillfix.log, haicom-305N.log, holux-gm-210.log, 
-     pharos-360.log, tn200-all.log, tn200.log, tn204.log
-notes = The bu* logs are in native binary format; the Haicom, Holux, Pharos, 
-      and TripNav logs in NMEA. NMEA starts with GGA and ends with RMC. The
-      tn204 NMEA looks remarkably like older Garmin cruft and may be emulating 
-      one, including the split reporting cycle.
-
-[SiRF-3]
-type = engine
-description = Version 3 of the SiRF GPS engine
-engine = SiRF-3
-nmea = 3.01
-uses = GenericSiRF
-rating = good
-logs = blumax-gps009.log, gpslim236.log, motorola-t805.log, rgm3800.log, et-332.log, tomtom-mkII.log
-notes = The Blumax log is in NMEA mode.  Start of cycle is GGA, End of cycle 
-      is RMC. Some variants (like the Blumax) emit ZDA before GGA; others 
-      (like the GPSlim 1236, Motorola T805, RGM3800) do not.
-
-[SiRF-4]
-type = engine
-description = Version 4 of the SiRF GPS engine
-engine = SiRF-4
-nmea = 3.01
-uses = GenericSiRF
-rating = poor
-logs = bu353s4.log
-notes = Low power usage, but poor sensitivity and very long startup.
-      Resets to 4800N1 every time it is unplugged. Has a tendency to freeze
-      when switched from binary to NMEA mode (unplugging it fixes this).
-
-[SiRF-TriG]
-type = engine
-description = Chinese variant of the SiRF GPS engine
-engine = SiRF-TriG
-nmea = 4.00
-uses = GenericSiRF
-#rating = poor
-logs = beidou-bd.log, beidou-gb.log
-notes = SiRF-IV variant produced for the Chinese market; it handles the
-      Beidou and GLONASS constellations as well as US GPS.  The main
-      variant is described by the Chinese standard "Technical
-      Specification of Communication Protocol for BDS Compatible
-      Positioning Module" (TSCPB) and uses the talker ID BD.  This
-      standard is not available in English translation. There is a
-      variant with closer NMEA 4.00 conformance that uses the talker
-      ID GB.
-
-[MSB2122]
-type = engine
-engine = MSB2122
-nmea = 2.3
-rating = good
-techdoc = http://www.mstar-europe.com/products.php
-notes = Code-named "Poseidon 2", this appears to be a MIPS core. May
-	ship with serious bugs that cause bogus fixes or hard crashes.
-
 [ANTARIS]
 type = engine
 engine = ANTARIS
@@ -185,6 +99,32 @@ notes = Sends 'E' in second field of GSA record, not an NMEA value.
       (This behavior reported on the 4H chipset.)
 logs = ublox-lea-4h.log, ublox-lea-4s.log, ublox-lea-4t.log
 
+[BD960]
+type = engine
+engine = BD960
+nmea = 3.0?
+tested = 2.39
+notes = Spec sheet says it emits GSV, AVR, RMC, HDT, VGK, VHD, GGLK, GGA, GSA,
+      ZDA, VTG, GST, and PIT in NMEA mode. Many of these are nonstandard.
+      Also says: "JK and Binary: Trimble GSOF".  Other web sources say
+      it has RTK capability.
+rating = good
+
+[FastraX iTrax03]
+type = engine
+techdoc = http://www.fastraxgps.com/products/gpsmodules/index.cfm?template=products.show.cfm&productGuid=4594da1a-503c-469c-91b2-6948043189be
+engine = FastraX iTrax03
+rating = good
+logs = com-1289.log
+notes = Start of fix cycle is RMC, end is GGA (GSVs may come after).
+
+[Garmin]
+type = engine
+engine = Garmin
+description = There are several versions; the differences are not clear.
+techdoc = http://www.garmin.com/support/commProtocol.html
+rating = good
+
 [LEA-5H]
 type = engine
 engine = LEA-5H
@@ -202,20 +142,22 @@ rating = good
 tested = 3.9
 notes = Appears not to have the ANTARIS4 GSA quirk. Excellent indoors.
 
-[FastraX iTrax03]
+[MSB2122]
 type = engine
-techdoc = http://www.fastraxgps.com/products/gpsmodules/index.cfm?template=products.show.cfm&productGuid=4594da1a-503c-469c-91b2-6948043189be
-engine = FastraX iTrax03
+engine = MSB2122
+nmea = 2.3
 rating = good
-logs = com-1289.log
-notes = Start of fix cycle is RMC, end is GGA (GSVs may come after).
+techdoc = http://www.mstar-europe.com/products.php
+notes = Code-named "Poseidon 2", this appears to be a MIPS core. May
+	ship with serious bugs that cause bogus fixes or hard crashes.
 
-[Garmin]
+[MT3339]
 type = engine
-engine = Garmin
-description = There are several versions; the differences are not clear.
-techdoc = http://www.garmin.com/support/commProtocol.html
+nmea = 3.01
+engine = MT3339
 rating = good
+techdoc = http://www.adafruit.com/datasheets/PMTK_A11.pdf
+notes = 10Hz update.
 
 [MTK]
 type = engine
@@ -249,47 +191,89 @@ type = engine
 engine = Pilot Plug
 rating = good
 
-[Sony CXD2951]
+[SE4100L]
 type = engine
-techdoc = http://gpsd.googlecode.com/files/cxd2951-commands.pdf
-engine = Sony CXD2951
-rating = good
+nmea = 3.01
+rating = fair
+notes = Does not handle dates after the 10-bit GPS week rollover in 2019 well.
+logs = gp-320fw-2019-03-28.log, gp-320fw-2019-03-28.log-overflow, gp-320fw-2019-03-28.log-coldboot
 
-[Touchstone ASIC]
+[SirfGeneric]
 type = engine
-engine = Touchstone ASIC
-rating = good
-techdoc = http://www.navcomtech.com/Products/GPS/Touchstone.cfm
+description = Capabilities generic to all SiRF chips
+# Sets 4800 baud shipping GGA+GSA+GSV+RMC
+to_nmea = 0xa0a200188102010100000101050101010000000100010001000112c00000b0b3
+to_native = $PSRF100,0,%b,8,1,0	# Sets 8N1 with specified speed
 
-[uNav]
+[SiRF-1]
 type = engine
-engine = uN3010
-nmea = 3.01
-notes = uNav was acquired by Atheros in 2007.  They have inherited
-      one GPS product, now designated uN3010.
+description = Version 1 of the SiRF GPS engine
+engine = SiRF-1
+nmea = 2.2
+uses = SirfGeneric
+tested = 2.34
 rating = good
+logs = ublox-sirf1.log
+notes = ublox-sirf1.log was made from a device with ublox firmware and
+      may not be typical of SiRF-1 chips.
 
-[Zodiac]
+[SiRF-2]
 type = engine
-engine = Zodiac
+description = Version 2 of the SiRF GPS engine
+engine = SiRF-2
+# Later versions may do 2.3
 nmea = 2.2
-tested = 2.0
-techdoc = http://www.gpskit.nl/downloads-en.htm
-notes = This chip was made by Rockwell International.  It was
-      also known as the Jupiter. It has been EOLed.
+uses = SirfGeneric
+tested = 2.37
 rating = good
-logs = zodiac.log
+logs = bu303b-nofix.log, bu303-climbing.log, bu303-moving.log,
+     bu303-nofix.log, bu303-stillfix.log, haicom-305N.log, holux-gm-210.log,
+     pharos-360.log, tn200-all.log, tn200.log, tn204.log
+notes = The bu* logs are in native binary format; the Haicom, Holux, Pharos,
+      and TripNav logs in NMEA. NMEA starts with GGA and ends with RMC. The
+      tn204 NMEA looks remarkably like older Garmin cruft and may be emulating
+      one, including the split reporting cycle.
 
-[BD960]
+[SiRF-3]
 type = engine
-engine = BD960
-nmea = 3.0?
-tested = 2.39
-notes = Spec sheet says it emits GSV, AVR, RMC, HDT, VGK, VHD, GGLK, GGA, GSA,
-      ZDA, VTG, GST, and PIT in NMEA mode. Many of these are nonstandard.
-      Also says: "JK and Binary: Trimble GSOF".  Other web sources say
-      it has RTK capability.
+description = Version 3 of the SiRF GPS engine
+engine = SiRF-3
+nmea = 3.01
+uses = SirfGeneric
 rating = good
+logs = blumax-gps009.log, gpslim236.log, motorola-t805.log, rgm3800.log, et-332.log, tomtom-mkII.log
+notes = The Blumax log is in NMEA mode.  Start of cycle is GGA, End of cycle
+      is RMC. Some variants (like the Blumax) emit ZDA before GGA; others
+      (like the GPSlim 1236, Motorola T805, RGM3800) do not.
+
+[SiRF-4]
+type = engine
+description = Version 4 of the SiRF GPS engine
+engine = SiRF-4
+nmea = 3.01
+uses = SirfGeneric
+rating = poor
+logs = bu353s4.log
+notes = Low power usage, but poor sensitivity and very long startup.
+      Resets to 4800N1 every time it is unplugged. Has a tendency to freeze
+      when switched from binary to NMEA mode (unplugging it fixes this).
+
+[SiRF-TriG]
+type = engine
+description = Chinese variant of the SiRF GPS engine
+engine = SiRF-TriG
+nmea = 4.00
+uses = SirfGeneric
+#rating = poor
+logs = beidou-bd.log, beidou-gb.log
+notes = SiRF-IV variant produced for the Chinese market; it handles the
+      Beidou and GLONASS constellations as well as US GPS.  The main
+      variant is described by the Chinese standard "Technical
+      Specification of Communication Protocol for BDS Compatible
+      Positioning Module" (TSCPB) and uses the talker ID BD.  This
+      standard is not available in English translation. There is a
+      variant with closer NMEA 4.00 conformance that uses the talker
+      ID GB.
 
 [Skytraq Venus 6]
 type = engine
@@ -297,6 +281,12 @@ nmea = 3.01
 rating = good
 tested = 2.90
 
+[Sony CXD2951]
+type = engine
+techdoc = http://gpsd.googlecode.com/files/cxd2951-commands.pdf
+engine = Sony CXD2951
+rating = good
+
 [STA8088]
 type = engine
 nmea = 2.2
@@ -304,6 +294,28 @@ rating = good
 tested = 3.7
 notes = From ST Microelectronics
 
+[Touchstone ASIC]
+type = engine
+engine = Touchstone ASIC
+rating = good
+techdoc = http://www.navcomtech.com/Products/GPS/Touchstone.cfm
+
+[uNav]
+type = engine
+engine = uN3010
+nmea = 3.01
+notes = uNav was acquired by Atheros in 2007.  They have inherited
+      one GPS product, now designated uN3010.
+rating = good
+
+[UBLOX M8030-KT]
+type = engine
+engine = M8030-KT
+rating = good
+tested = 3.14
+notes = Supports GPS, GLONASS, Galileo, BeiDou, QZSS and SBAS.  a.k.a NEO-M8N
+logs = neo-m8n.log
+
 [UBLOX NEO-5Q]
 type = engine
 nmea = 2.3
@@ -311,17 +323,25 @@ rating = good
 tested = 2.39
 notes = Supports WAAS.
 
-[SE4100L]
+[Zodiac]
 type = engine
-nmea = 3.01
-rating = fair
-notes = Does not handle dates after the 10-bit GPS week rollover in 2019 well.
-logs = gp-320fw-2019-03-28.log, gp-320fw-2019-03-28.log-overflow, gp-320fw-2019-03-28.log-coldboot
+engine = Zodiac
+nmea = 2.2
+tested = 2.0
+techdoc = http://www.gpskit.nl/downloads-en.htm
+notes = This chip was made by Rockwell International.  It was
+      also known as the Jupiter. It has been EOLed.
+rating = good
+logs = zodiac.log
 
 #
 # Vendors (alphabetical by vendor)
 #
 
+[Adafruit]
+type = vendor
+vendor_site = https://www.adafruit.com/
+
 [Altina]
 type = vendor
 vendor_site = http://www.altina.com
@@ -334,6 +354,10 @@ vendor_site = http://www.adapt-mobile.com>
 type = vendor
 vendor_site = http://code.google.com/p/gpsd/downloads/detail?name=SiRF-Axiom.pdf&can=2&q=
 
+[BeStar]
+type = vendor
+vendor_site = http://www.sz-beitian.com/
+
 [Billionton]
 type = vendor
 vendor_site = http://www.billionton.com/english/index.htm
@@ -548,6 +572,22 @@ vendor_site = http://www.wintec.com.tw/
 # Devices (alphabetical by vendor)
 #
 
+#% Adafruit
+
+[Ultimate GPS HAT]
+type = device
+packaging = HAT
+vendor = Adafruit
+techdoc = https://learn.adafruit.com/adafruit-ultimate-gps-hat-for-raspberry-pi
+interfaces = Raspberry Pi HAT
+tested = 3.14
+rating = excellent
+uses = MT3339
+pps = Yes
+submitter = Gary E. Miller <gem@rellim.com>
+notes = Built-in antenna with conenctor for external antenna. Good, not
+        great sensitivity with built-in antenna.  Built-in RTC and battery.
+
 #% Altina
 
 [GBT709]
@@ -592,6 +632,22 @@ notes = The vendor is out of business, but there are lots of these still
       around in 2006.  Complete documentation for this OEM module has been
       archived at the GPSD site.
 
+#% BeStar
+
+[BN-880]
+type = device
+vendor = BeStar
+packaging = OEM module
+uses = UBLOX M8030-KT
+interfaces = LV RS-232
+tested = 3.14
+rating = excellent
+submitter = Gary E. Miller <gem@rellim.com>
+pps = False
+notes = Vendor is in Shenzhen, China.  Frequently on eBay.  Sold as a
+      'Flight Control Module' as it also contains  gyros and acceleromters
+      in a separate I2C bus.  Does not have PPS but some resellers claim PPS.
+
 #% Billionton
 
 [Billionton CF-GPS]
@@ -613,7 +669,7 @@ notes = Uses SiRF firmware version 220.006.000ES. Accepts WAAS Mode Disable
 type = device
 engine = Skytraq Venus 6
 date = 2010-06-10
-location = 
+location =
 model = BN-901S
 packaging = mouse
 interfaces = Bluetooth
@@ -793,8 +849,8 @@ interfaces = RS-232
 location = Ulb?lle, DK, 55.04N 10.25E
 model = Foretrex 201
 nmea = 3.0
-notes = This device is not a conventional handfrtee unut for a car; it looks 
-      like a bulky wristwatch and is meant for bicycle handlebars. It must 
+notes = This device is not a conventional handfrtee unut for a car; it looks
+      like a bulky wristwatch and is meant for bicycle handlebars. It must
       be set to NMEA output in the settings->interface page.
 packaging = handset
 rating = excellent
@@ -845,7 +901,7 @@ uses = Garmin
 interfaces = RS-232
 tested = 2.38
 nmea = 2.0
-submitter = Reported by Ron Marosko, Jr. <rmarosko@wirelessfrontier.net>, 
+submitter = Reported by Ron Marosko, Jr. <rmarosko@wirelessfrontier.net>,
       Amaury Jacquot <sxpert@esitcom.org>,
       Jeff Francis <jfrancis@gritch.org>
 notes = DGPS information in GPGGA sentence is not returned. Satellite
@@ -957,7 +1013,7 @@ nmea = 2.0
 discontinued = True
 rating = excellent
 tested = regression
-notes = Start-of-cycle is RMC. 2-second cycle time, 2 fixes per cycle, GLL 
+notes = Start-of-cycle is RMC. 2-second cycle time, 2 fixes per cycle, GLL
       reports second fix. The 48 has been discontinued.  The Garmin
       12XL and 45 are nearly identical and should work as well.
       Details on the Garmin proprietary protocol can be found at <a
@@ -983,13 +1039,13 @@ uses = Garmin
 interfaces = RS-232
 tested = 2.39
 nmea = 2.3
-submitter = Sebastian Niehaus <killedbythoughts@mindcrime.net>, 
+submitter = Sebastian Niehaus <killedbythoughts@mindcrime.net>,
 	  Geoff Childs <dofinch-aria@yahoo.co.uk>
-notes = The device has a four pin socket described by Garmin as a serial 
-      interface. Connection to a standard 9 pin RS-232 computer socket 
+notes = The device has a four pin socket described by Garmin as a serial
+      interface. Connection to a standard 9 pin RS-232 computer socket
       is made using the special adaptor lead supplied by Garmin.  Sebastian
       Niehaus says it annunces "Software Version 3.70". Geoff Childs adds:
-      "The Garmin GPS 76 comms MUST be set to 'NMEA'. The kernel module 
+      "The Garmin GPS 76 comms MUST be set to 'NMEA'. The kernel module
       garmin_gps is not needed and should not be specially loaded."
 
 [Geko 201]
@@ -1002,7 +1058,7 @@ interfaces = RS-232
 tested = regression
 nmea = 3.0
 submitter = Jose Luis Domingo Lopez <jdomingo@24x7linux.com>
-notes = 
+notes =
 logs = garmin-geko201.log
 
 [eTrex Vista]
@@ -1015,7 +1071,7 @@ interfaces = RS-232
 tested = 2.32
 nmea = 3.0
 submitter = Reed Hedges <reed@interreality.org>
-notes = 
+notes =
 
 [Nuvi 650]
 type = device
@@ -1027,7 +1083,7 @@ interfaces = USB
 tested = *
 nmea = 3.0
 rating = broken
-notes = This device does not have real-time data output, and is incompatible 
+notes = This device does not have real-time data output, and is incompatible
       with GPSD.
 
 [GPSmap 76S]
@@ -1095,7 +1151,7 @@ submitter = Viktar Palstsiuk <viktar.palstsiuk@promwad.com>
 techdoc = http://geostar-navigation.com/fail/manuals/User_Manual_GeoS-1M_en.pdf
 tested = 2.90
 vendor = Geostar
-notes = GeoS-1M is the combined GPS/GLONASS OEM receiver board. Its 
+notes = GeoS-1M is the combined GPS/GLONASS OEM receiver board. Its
       architecture includes 24 tracking channels.
 logs = geos-1m.log
 
@@ -1151,7 +1207,7 @@ tested = regression
 rating = excellent
 eval_unit = esr
 nmea = 2.2
-notes = Older versions of the BU-303 had a design defect that made it 
+notes = Older versions of the BU-303 had a design defect that made it
         likely to fail if subjected to vibration or hard shocks.
 
 [BU-353]
@@ -1263,8 +1319,8 @@ tested = 3.3
 type = device
 uses = SiRF-3
 vendor = GlobalSat
-notes = May work inside wood frame buildings.  PPS pulse is only 1uS wide, 
-      but newer gpsd handles that fine. Be careful, there is also an MR-350 
+notes = May work inside wood frame buildings.  PPS pulse is only 1uS wide,
+      but newer gpsd handles that fine. Be careful, there is also an MR-350
       (no suffix P) that does NOT have PPS.
 logs = mr-350p
 
@@ -1486,7 +1542,7 @@ notes = The product page points at a retail site carrying these
       because the vendor site is in Japanese only.  This GPS emits a
       weirdly broken GSA sentence that crashed gpsd versions prior to
       2.28. Serial parameters default to 38400; 8, N, 1.  May come
-      bundled with Microsoft Streets and Trips. 
+      bundled with Microsoft Streets and Trips.
 logs = iTrek.log
 
 #% Jackson Labs
@@ -1500,14 +1556,14 @@ pps = True
 pps_accuracy = 50ns
 packaging = OEM module
 rating = excellent
-submitter = Don Weeks <don.l.weeks.jr@gmail.com>, 
+submitter = Don Weeks <don.l.weeks.jr@gmail.com>,
             Said Jackson <saidjack@aol.com>
 techdoc = http://jackson-labs.com/docs/FireFly_quickstart.pdf
 vendor = Jackson Labs
-notes = Only outputs GGA and RMC NMEA strings. There are other proprietary 
-        commands. See the gpsd-dev list for patches. GPSD works as far back 
-        as the 0.914 version, which emitted \r\r\n terminations. All the 
-        FireFly units are OCXO driven, so the 1PPS output stays accurate even 
+notes = Only outputs GGA and RMC NMEA strings. There are other proprietary
+        commands. See the gpsd-dev list for patches. GPSD works as far back
+        as the 0.914 version, which emitted \r\r\n terminations. All the
+        FireFly units are OCXO driven, so the 1PPS output stays accurate even
         if GPS reception is lost.
 
 [FireFly-II]
@@ -1520,10 +1576,10 @@ pps = True
 pps_accuracy = 50ns
 time_offset = ?
 model = FireFly-1A and FireFly-II GPSDO
-notes = Uses ublox Antaris 5 with Kick Start and Super Sense, 
+notes = Uses ublox Antaris 5 with Kick Start and Super Sense,
         soon movingto ublox-6.  Defective \r\r\n string terminations
-        have been fixed in the 2.18 firmware version. All the 
-        FireFly units are OCXO driven, so the 1PPS output stays accurate even 
+        have been fixed in the 2.18 firmware version. All the
+        FireFly units are OCXO driven, so the 1PPS output stays accurate even
         if GPS reception is lost.
 packaging = OEM module
 rating = good
@@ -1577,7 +1633,7 @@ interfaces = RS-232
 tested = regression
 rating = good
 submitter = Angel Marques Mateu <amarques@cgf.upv.es>
-notes = 
+notes =
 logs = magellan315.log
 
 [Meridian Platinum]
@@ -1603,7 +1659,7 @@ interfaces = USB
 tested = regression
 rating = good
 nmea = 2.1
-submitter = rickyconnell@gmail.com 
+submitter = rickyconnell@gmail.com
 logs = eXplorist110.log
 
 [eXplorist 210]
@@ -1621,7 +1677,7 @@ notes = USB has 3 modes &mdash; NMEA data comm (3 submodes): outputs GPS data
       (creates /dev/ttyACM0), USB file transfer: transfer files (creates
       /dev/sdX and /dev/sdX1), or Power Only: use USB only for electrical
       power.  The APA and XTE extensions choke gpsd, so select V2.1 GSA
-      under "NMEA Data Comm>". 
+      under "NMEA Data Comm>".
 logs = eXplorist210.log
 
 [Thales AC12]
@@ -1783,7 +1839,7 @@ notes = When running, need to use the -b option, else the device will
       "fudge" factor to 0.840. There is no known PPS signal associated
       with this device.  While the technical information claims 1us
       accuracy on the clock, the interface is undocumented, so there
-      is no way to know if there is a usable 1PPS signal. 
+      is no way to know if there is a usable 1PPS signal.
 
 [NL-302U]
 type = device
@@ -1882,8 +1938,8 @@ techdoc = http://navis.ru/downloads/CH-4711_USB/
 logs = ch-4711.log
 notes = By default the device does not report 2d fixes; the vendor
       configuration tool offers checkboxes to enable any combination of
-      none, 2D fixes, 3D fixes, or both.  The devices has only a very 
-      limited set of NMEA controls but speaks a proprietary vendor format 
+      none, 2D fixes, 3D fixes, or both.  The devices has only a very
+      limited set of NMEA controls but speaks a proprietary vendor format
       called BINR with more capabilities.
 
 [NAVIOR-24]
@@ -1919,12 +1975,12 @@ submitter = sk1ppy14@yahoo.co.uk
 techdoc = http://www.navisys.com.tw/products/image/GR-300_flyer-080409.pdf
 tested = 2.38
 vendor = Navisys
-notes = Also includes an (untested) Bluetooth interface. Has two LEDs: 
-      blue for bluetooth, green for rating. Solid green = on and searching 
+notes = Also includes an (untested) Bluetooth interface. Has two LEDs:
+      blue for bluetooth, green for rating. Solid green = on and searching
       for satellite fixes. Blinking green = on and has 3D fix.
-      Also a similar GR-310 version available. It is possible that only GR-310 
-      supports Bluetooth. Programs only seem to be able to communicate 
-      with the dongle at 4800 baud rates, though this is autodetected by gpsd 
+      Also a similar GR-310 version available. It is possible that only GR-310
+      supports Bluetooth. Programs only seem to be able to communicate
+      with the dongle at 4800 baud rates, though this is autodetected by gpsd
       with no problems. Approx &pound;40 per <a href="http://www.navisys.com.tw/products/gps_usb_dongle.htm">dongle</a>.
 
 #%Nokia
@@ -2029,7 +2085,7 @@ tested = 2.34
 nmea = 2.2
 notes = As this is a Bluetooth device, gpsd must either be run with "-b" or must
       be compiled with fixed port speed, as the Bluetooth interface does not
-      tolerate port speed changes at all. Reported by Sebastiano Zabert 
+      tolerate port speed changes at all. Reported by Sebastiano Zabert
       (no emal address)
 
 #% Qstarz
@@ -2063,7 +2119,7 @@ rating = fair
 submitter = Stoo <f4eru@free.fr>
 techdoc = http://www.rfsolutions.co.uk/acatalog/DS320-2.pdf
 vendor = RF Solutions
-notes = Has a binary protcol documetened at 
+notes = Has a binary protcol documetened at
       http://www.rfsolutions.co.uk/acatalog/DS-41COM-2.pdf.
       Sat-simulator testing reveals that the chipset does not handle
       dates after 2019 well; they wrap to 1999. The device sends out
@@ -2569,7 +2625,7 @@ usbchip = CP2101
 tested = 3.4
 nmea = 3.01
 submitter = Reported by Eric S. Raymond <esr@thyrsus.com>
-notes = Device has two variants; the basic receiver is 'R' and the 
+notes = Device has two variants; the basic receiver is 'R' and the
       version with additional data-logger capability is N.  Emits only NMEA.
       Some Web sources incorrectly describe it as SiRF-3-based.