X-Git-Url: https://sigrok.org/gitweb/?a=blobdiff_plain;f=README.devices;h=f28462a02977a2dc2d5da968fd98d7ed0be67e8d;hb=f57924179d08dee9d24099233ffbee2123613a22;hp=3e981ec73e3e1d86c7d2f460c81d1f1dc0898bc2;hpb=1b142b78274d74563a084299a01ef1a92206356f;p=libsigrok.git

diff --git a/README.devices b/README.devices
index 3e981ec7..f28462a0 100644
--- a/README.devices
+++ b/README.devices
@@ -64,9 +64,11 @@ The following drivers/devices do not need any firmware upload:
  - lascar-el-usb
  - link-mso19
  - mic-985xx
+ - norma-dmm
  - openbench-logic-sniffer
  - rigol-ds1xx2
  - serial-dmm
+ - teleinfo
  - tondaj-sl-814
  - uni-t-dmm
  - uni-t-ut32x
@@ -98,8 +100,10 @@ The following drivers/devices require a serial port specification:
  - fluke-dmm
  - link-mso19
  - mic-985xx
+ - norma-dmm
  - openbench-logic-sniffer
  - serial-dmm
+ - teleinfo
  - tondaj-sl-814
 
 The following drivers/devices do not require a serial port specification:
@@ -214,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).
 
+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
@@ -221,8 +229,8 @@ to access the respective USB device (see above).
 
 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