aboutsummaryrefslogtreecommitdiff
path: root/README.Windows
diff options
context:
space:
mode:
authorAndreas Fritiofson <andreas.fritiofson@gmail.com>2014-03-22 14:09:06 +0100
committerSpencer Oliver <spen@spen-soft.co.uk>2014-03-28 10:07:01 +0000
commit09e9625d6ce52bbed271c1087df58fb3bb78b99a (patch)
tree6cf39dbf62e72208ce4e3a75c33106307f707638 /README.Windows
parent075c3f8fe29c7aecd446c655a7fadb9e1999a31f (diff)
ft2232: Mark interface driver as deprecated
Change-Id: I5ebc924ab66c86f1902942bebc203a34d97abc64 Signed-off-by: Andreas Fritiofson <andreas.fritiofson@gmail.com> Reviewed-on: http://openocd.zylin.com/1899 Reviewed-by: Paul Fertser <fercerpav@gmail.com> Reviewed-by: Spencer Oliver <spen@spen-soft.co.uk> Tested-by: Spencer Oliver <spen@spen-soft.co.uk>
Diffstat (limited to 'README.Windows')
-rw-r--r--README.Windows15
1 files changed, 15 insertions, 0 deletions
diff --git a/README.Windows b/README.Windows
index 61a712ab..9cdd55c5 100644
--- a/README.Windows
+++ b/README.Windows
@@ -32,3 +32,18 @@ WinUSB to a device is to use the latest Zadig installer:
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