be compatible with libusb-versions without dev->devnum member

[usb-driver] / README

diff --git a/README b/README
index 1498a9aa78a969e5bc6e17c770381ea01559db77..a05ae7cbbb0761a021ebdcc69babf60d779fd3db 100644 (file)
--- a/README
+++ b/README
@@ -9,22 +9,28 @@ should work on every kernel version which is supported by libusb and supports
 ppdev. It was written against impact from ISE Webpack 9.1SP1 and tested with
 the following software:
 
+ * ISE Webpack 9.2SP1
  * ISE Webpack 9.1SP3
  * ISE Webpack 9.1SP2
  * ISE Webpack 9.1SP1
  * ISE Webpack 8.2SP3
  * ISE Webpack 8.1SP3
+ * ChipScope 9.2.01i
  * ChipScope 9.1.03i
  * ChipScope 9.1.02i
  * ChipScope 8.2.04i
+ * EDK 9.1.02i
+ * EDK 9.1.01i
  * EDK 8.2.02i
  * EDK 8.1.02i
+ * Synplicity Identify
 
 In addition to the XILINX USB and parallel cables, devices based on the FTDI
 2232 serial converter chip are also experimentally supported. This includes
 devices like the Amontec JTAGkey(-Tiny).
 
-Build the library by calling `make'.
+Build the library by calling `make'. If you are on a 64 bit system but want
+to build a 32 bit library, run `make lib32' instead.
 
 To use this library you have to preload the library before starting impact:
 
@@ -63,11 +69,19 @@ these steps:
 2. Install the package containing /sbin/fxload from your linux distribution.
    It is usually called "fxload"
 
-3. copy the file /path/to/ISE/bin/lin/xusbdfwu.hex to /usr/share/xusbdfwu.hex
+3. copy the files /path/to/ISE/bin/lin/xusb*.hex to /usr/share/
 
 4. restart udev and re-plug the cable
 
 
+If you have multiple cables connected, you can specify the cable to use
+in the XILINX_USB_DEV environment-variable as "bus:device".
+These identifiers are available in the output of lsusb:
+Bus 001 Device 004: ID 03fd:0008 Xilinx, Inc.
+    ^^^        ^^^
+To use this cable, set the XILINX_USB_DEV variable to "001:004".
+
+
 Notes for the parallel cable
 ============================
 
@@ -129,3 +143,12 @@ To set-up the device:
 
 The support for FTDI 2232 based devices is experimental and they are currently
 significantly slower than the other supported cables.
+
+
+Locked cables
+=============
+
+If you get the message 'The cable is being used by another application.' from
+impact, try running the following command:
+
+echo -e 'cleancablelock\nexit' | impact -batch