ft2232: Mark interface driver as deprecated

[openocd.git] / README.Windows

diff --git a/README.Windows b/README.Windows
index f923228af877b2e71afb6dc76e4dfbb69bd9794c..9cdd55c5c2236b53de19bbc2384fd7fe3a893a9f 100644 (file)
--- a/README.Windows
+++ b/README.Windows
@@ -1,11 +1,13 @@
 Building OpenOCD for Windows
 ----------------------------
 
-You can build OpenOCD for Windows natively with either MinGW/MSYS or
-Cygwin. Alternatively, one can cross-compile it using MinGW on a *nix
+You can build OpenOCD for Windows natively with either MinGW-w64/MSYS
+or Cygwin (plain MinGW might work with --disable-werror but is not
+recommended as it doesn't provide enough C99 compatibility).
+Alternatively, one can cross-compile it using MinGW-w64 on a *nix
 host. See README for the generic instructions.
 
-Native MinGW/MSYS compilation
+Native MinGW-w64/MSYS compilation
 -----------------------------
 
 As MSYS doesn't come with pkg-config pre-installed, you need to add it
@@ -14,7 +16,7 @@ from:
 
   http://sourceforge.net/projects/pkgconfiglite/
 
-Then simply unzip the archive to the root directory of your MSYS
+Then simply unzip the archive to the root directory of your MinGW-w64
 installation.
 
 USB adapters
@@ -23,10 +25,25 @@ USB adapters
 You usually need to have WinUSB.sys (or libusbK.sys) driver installed
 for a USB-based adapter. Some vendor software (e.g. for ST-LINKv2)
 does it on its own. For the other cases the easiest way to assign
-WinUSB to a device is to use the Zadig installer:
+WinUSB to a device is to use the latest Zadig installer:
 
-  http://sourceforge.net/projects/libwdi/files/zadig/
+  http://zadig.akeo.ie
 
 For the old drivers that use libusb-0.1 API you might need to link
 against libusb-win32 headers and install the corresponding driver with
 Zadig.
+
+If you need to use the same adapter with other applications that may
+require another driver, a solution for Windows Vista and above is to
+activate the IgnoreHWSerNum registry setting for the USB device.
+
+That setting forces Windows to associate the driver per port instead of
+per serial number, the same behaviour as when the device does not contain
+a serial number. So different drivers can be installed for the adapter on
+different ports and you just need to plug the adapter into the correct
+port depending on which application to use.
+
+For more information, see:
+
+  http://msdn.microsoft.com/en-us/library/windows/hardware/jj649944(v=vs.85).aspx
+  http://www.ftdichip.com/Support/Knowledgebase/index.html?ignorehardwareserialnumber.htm