mifr/subsurface
1
0
Fork 0
mirror of https://github.com/subsurface/subsurface.git synced 2025-02-17 19:36:15 +00:00
Code Issues Projects Releases Packages Wiki Activity

documentation: additional explanations around Windows USB drivers

Browse source 
This is adapted from a conversation with Jef.

Suggested-by: Jef Driesen <jef@libdivecomputer.org>
Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
This commit is contained in:
Dirk Hohndel 2020-02-25 10:27:32 -08:00
parent fb18bc0803
commit 9214bdb3c5
1 changed files with 12 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
Documentation/user-manual.txt
View file

@ -4406,7 +4406,18 @@ computer prefers (e.g. Bluetooth, USB, infra-red).
* On Windows, the OS should offer to download the correct
driver once the user connects the dive computer to the USB port and
operating system sees the equipment for the first time.
operating system sees the equipment for the first time. In some instances this
seems to fail, but regardless, every USB device (with the exception of HID devices
like the Suunto EON Steel family) needs a driver. For many divecomputer this means
downloading a cable specific driver (these tend to be for example FTDI, Silicon Labs,
or Prolific drivers). In other cases (for example for dive computers with a "real" USB
interface like the Atomics Cobalt) it is sufficient to have the WinUSB (or the libusbK)
driver installed. In current Windows versions the WinUSB binary is already part of Windows
and the "driver" is a simple inf file that tell Windows to use the WinUSB driver. But it
still needs to be "installed". Often it is sufficient to install the dive log app that is
provided by the dive computer vendor to trigger the driver installation. But in cases
where that doesn't work, some googling to find the correct driver for a specific download
cable may be necessary.
* On a Mac users sometimes have to manually hunt for the correct
driver. For example the correct driver for the Mares Puck