diff options
Diffstat (limited to 'gpscap.ini')
| -rw-r--r-- | gpscap.ini | 36 |
1 files changed, 19 insertions, 17 deletions
@@ -5,7 +5,7 @@ # # Each section map have the following capabilities # -# type = "engine", "vendor", or "device" +# type = "engine", "vendor", or "device" # description = Human-readable description of this item # packaging = A device's form factor # reference = URL to technical documentation, or at least a spec sheet @@ -16,11 +16,11 @@ # subtype = engine subtype or firmware revision level # interfaces = interface types: USB, RS232, Bluetooth, CF, TTL. May be a list. # usbchip = USB I/O chipset -# pps = supports pulse-per-second precision time reporting -# btglitch = has bluetooth glitch (requires -b option) +# pps = supports pulse-per-second precision time reporting +# noconfigure = can be bricked by baud-rate changes (requires -b option) # tested = last gpsd tested, or "regression" if we have a test load -# nmea = NMEA version this emits, if known -# notes = Miscellaneous notes on this item. To be interpreted as HTML. +# nmea = NMEA version this emits, if known +# notes = Miscellaneous notes on this item. To be interpreted as HTML. # status = excellent, good, fair, poor, broken, other # discontinued = If present, product has been discontinued # @@ -313,7 +313,7 @@ vendor = Altina packaging = handset reference = http://www.altina.com/produkty.php?destCatId=&mainCatId=13&subCatId=&prId=19 interfaces = Bluetooth -btglitch = yes +noconfigure = True tested = 2.35 uses = SiRF-3 notes = Requires the "-b" flag to prevent mode switching. If the receiver locks @@ -372,7 +372,7 @@ reference = http://www.cpit.com/en/GP-27.html uses = Nemerix interfaces = Bluetooth tested = 2.28 -btglitch = yes +noconfigure = True notes = Reported by Tobias Minich <belgabor@gmx.de> <ul> <li>There are proprietary PNMRX{30[0124],603} sentences that are only sent on change or by request</li> @@ -442,7 +442,7 @@ packaging = GPS mouse reference = http://www.eurotronic.net/products/produktdetails/gps_receiver.html uses = SiRF-3 interfaces = Bluetooth -btglitch = yes +noconfigure = True tested = regression notes = Requires "-b" ... I had to totally drain the battery of the device and let it rest for a few days before i was able to use it again @@ -815,7 +815,7 @@ packaging = GPS mouse reference = http://www.holux.com.tw/Temp%20web/GR-230.html uses = SiRF-2 interfaces = Bluetooth -btglitch = yes +noconfigure = True tested = 2.19 nmea = 2.2 discontinued = True @@ -853,7 +853,7 @@ packaging = GPS mouse reference = http://www.holux.com/JCore/en/support/DLF.jsp?DLU=http://www1.holux.com.tw:8080/JCore/UploadFile/79754.pdf uses = SiRF-3 interfaces = Bluetooth, USB -btglitch = yes +noconfigure = True tested = 2.36 status = poor nmea = 2.2 @@ -868,7 +868,7 @@ reference = http://www.holux.com/JCore/en/products/products_content.jsp?pno=341 uses = MKT interfaces = Bluetooth, USB usbchip = CP2101 -btglitch = yes +noconfigure = True tested = 2.37 notes = gpsd crashes the device when autoprobing @ baud rate 9600 (unless '-b'/broken-device-safety is enabled - need to unplug/reset the device). @@ -1052,7 +1052,7 @@ packaging = GPS mouse reference = http://www.navilock.de/produkte/gruppen/3/Kabel_Empfaenger/61371_NL-209PU.html?show=spec uses = Sony CXD2951 interfaces = USB, RS232, Bluetooth -btglitch = yes +noconfigure = True usbchip = pl2303 tested = 2.35 nmea = 2.2 @@ -1154,7 +1154,7 @@ packaging = GPS mouse reference = http://www.phonix.it/html/catalogo_dettaglio.cfm?idProducts=E09B5AB7-BCDF-DF66-24853E2B4680AB2C uses = SiRF-2 interfaces = Bluetooth -btglitch = yes +noconfigure = True tested = 2.34 nmea = 2.2 notes = Reported by Sebastiano Zabert<br/> @@ -1413,15 +1413,17 @@ vendor = UniTraq packaging = GPS mouse reference = http://www.wintec.com.tw/en/support_detail.php?cate_id=11&support_id=14 uses = Sony CXD2951 -btglitch = yes +noconfigure = True interfaces = USB usbchip = Silicon Laboratories CP2101 tested = 2.35 nmea = 3.0 notes = This receiver operates as a generic NMEA device, the Sony binary protocol is unsupported. The receiver seems to lock up if - too much data is thrown at it (ie. gpsd probes) thus it seems to - require a read-only (-b) instance of gpsd. Reported by Ian - Darwin <ian@darwinsys.com> + too much data is thrown at it (ie. gpsd probes) thus it may + require a read-only (-b) instance of gpsd. (We say 'may' because + more recent instances of gpsd break the probe writes into pieces + interleaved with read, and may no longer trigger this problem) + Reported by Ian Darwin <ian@darwinsys.com> |