X-Git-Url: https://git.gag.com/?a=blobdiff_plain;f=doc%2Fopenocd.texi;h=7f13f042726e8f1b24401480cf81fd0dcf977aa3;hb=ac1bd155c20d38eec1400fece84c18420f35e802;hp=551b62c5459c8591b2b73a14796510ea02d8cb08;hpb=ee8a6788df5c5e765ae102821a91f49cfc0dc05a;p=fw%2Fopenocd

diff --git a/doc/openocd.texi b/doc/openocd.texi
index 551b62c54..7f13f0427 100644
--- a/doc/openocd.texi
+++ b/doc/openocd.texi
@@ -126,8 +126,8 @@ a FTDI FT2232 based interface:
 homepage (@uref{www.amontec.com}), as the JTAGkey uses a non-standard VID/PID. 
 @end itemize
 
-Please note that the ftdi2232 variant (using libftdi) isn't supported under Cygwin.
-You have to use the ftd2xx variant (using FTDI's D2XX) on Cygwin.
+libftdi is supported under windows. Versions earlier than 0.13 will require patching.
+see contrib/libftdi for more details.
 
 In general, the D2XX driver provides superior performance (several times as fast),
 but has the draw-back of being binary-only - though that isn't that bad, as it isn't
@@ -481,7 +481,10 @@ OOCDLink
 
 @item @b{ft2232_vid_pid} <@var{vid}> <@var{pid}>
 The vendor ID and product ID of the FTDI FT2232 device. If not specified, the FTDI
-default values are used. This command is not available on Windows. 
+default values are used. Multiple <@var{vid}>, <@var{pid}> pairs may be given, eg.
+@smallexample
+ft2232_vid_pid 0x0403 0xcff8 0x15ba 0x0003
+@end smallexample
 @item @b{ft2232_latency} <@var{ms}>
 On some systems using ft2232 based JTAG interfaces the FT_Read function call in
 ft2232_read() fails to return the expected number of bytes. This can be caused by