fx2lafw: Minor cleanups.

[libsigrok.git] / README.devices

diff --git a/README.devices b/README.devices
index ecd2ffc0670e029a233f3a55b3adb81ebc5bcaea..a99fc7e2e95f8fb0e9783e99c7adf8f0022b533c 100644 (file)
--- a/README.devices
+++ b/README.devices
@@ -66,7 +66,7 @@ The following drivers/devices do not need any firmware upload:
  - mic-985xx
  - norma-dmm
  - openbench-logic-sniffer
  - mic-985xx
  - norma-dmm
  - openbench-logic-sniffer

- - rigol-ds1xx2
+ - rigol-ds

  - serial-dmm
  - teleinfo
  - tondaj-sl-814
  - serial-dmm
  - teleinfo
  - tondaj-sl-814


@@ -118,7 +118,7 @@ The following drivers/devices do not require a serial port specification:
  - ikalogic-scanaplus
  - kecheng-kc-330b
  - lascar-el-usb
  - ikalogic-scanaplus
  - kecheng-kc-330b
  - lascar-el-usb

- - rigol-ds1xx2
+ - rigol-ds

  - saleae-logic16
  - uni-t-dmm
  - uni-t-ut32x
  - saleae-logic16
  - uni-t-dmm
  - uni-t-ut32x


@@ -218,6 +218,10 @@ When using any of the UT-D04 USB/HID cables you have to use the respective
 driver _without_ the '-ser' drivername suffix (internally all of these models
 are handled by the 'uni-t-dmm' driver).
 
 driver _without_ the '-ser' drivername suffix (internally all of these models
 are handled by the 'uni-t-dmm' driver).
 

+You also need to specify the USB vendor/device IDs of the cable.
+Autodetection is not possible here, since various other products use the
+USB VID/PID of those cables too, and there is no way to distinguish them.
+

 Since the UT-D04 cables are USB based (but don't use a USB-to-serial chip)
 there is no need to specify a serial port via 'conn', of course.
 However, the user running the frontend does also need to have permissions
 Since the UT-D04 cables are USB based (but don't use a USB-to-serial chip)
 there is no need to specify a serial port via 'conn', of course.
 However, the user running the frontend does also need to have permissions


@@ -225,8 +229,8 @@ to access the respective USB device (see above).
 
 Examples (sigrok-cli):
 
 
 Examples (sigrok-cli):
 

- $ sigrok-cli --driver uni-t-ut61e ...
- $ sigrok-cli --driver voltcraft-vc820 ...
+ $ sigrok-cli --driver uni-t-ut61e:conn=1a86.e008 ...
+ $ sigrok-cli --driver voltcraft-vc820:conn=04fa.2490 ...

 
 
 UNI-T UT-D04 cable issue on Linux
 
 
 UNI-T UT-D04 cable issue on Linux


@@ -340,12 +344,12 @@ Example:
  $ sigrok-cli --driver ols:conn=/dev/ttyACM0 ...
 
 
  $ sigrok-cli --driver ols:conn=/dev/ttyACM0 ...
 
 

-Rigol DS1xx2 oscilloscopes
---------------------------
+Rigol DS oscilloscopes
+----------------------

 
 

-The 'rigol-ds1xx2' driver (for the Rigol DS1052E and some other, similar DSOs)
-currently uses the Linux usbtmc kernel driver. This means it can currently
-only be built and used on Linux (i.e., it's non-portable).
+The 'rigol-ds' driver (for the Rigol DS series DSOs) currently uses the Linux
+usbtmc kernel driver. This means it can currently only be built and used on
+Linux (i.e., it's non-portable).

 
 The use of a kernel module also means it is dependent on the kernel version
 used, as well as on whether this specific module is available in the kernel.
 
 The use of a kernel module also means it is dependent on the kernel version
 used, as well as on whether this specific module is available in the kernel.


@@ -356,4 +360,3 @@ module as opposed to a libusb-based driver that works in user-space.
 We plan to change the driver to use the 'librevisa' user-space shared
 library (which uses libusb) soon, which will fix all these issues and make
 the driver portable at the same time.
 We plan to change the driver to use the 'librevisa' user-space shared
 library (which uses libusb) soon, which will fix all these issues and make
 the driver portable at the same time.

-