On Sun, Jun 21, 2009 at 7:15 PM, Xiaofan Chen<xiaof...@gmail.com> wrote: > On Sun, Jun 21, 2009 at 7:08 PM, Michael Fischer<fische...@t-online.de> wrote: >> Hello List, >> >> an hacked version of libusb0.sys is not needed anymore. >> With the hacked version it is still not allowed to distribute >> it because how should the user create the hacked version? >> >> I could build a libusb driver based on SVN trunk version 161, >> under MinGW. The drivers version is 1.0.0.0. >> This driver will support the setting of composite devices >> in the inf file. >> >> Unfortunately I could only build the x32 verison and no x64. >> >> Btw, this will not solve the need of the FTD2XX, but now we >> can distribute a libusb composite version. > > That is great. I can help build the 64bit version of libusb-win32 > svn version and send it to you later. > > You can also try to build it by yourself. > > 1) You can download the old DDK version here. > http://www.microsoft.com/whdc/devtools/ddk/default.mspx > > 2) You can get latest WDK here. You need to use > Microsoft Connect. > http://www.microsoft.com/whdc/DevTools/WDK/WDKpkg.mspx >
The moot point is that the 64bit libusb-win32 driver is only working under Windows XP 64 bit which does not have many users. It is not working under Vista 64 without some hacking. And I am not sure if OpenOCD built with MinGW can be used with the driver built with DDK/WDK (using compiler similar to Visual C++) for XP 64. I am not sure we can build OpenOCD with Visual C++ as of now. Moreover, I do not have XP 64 or Vista 64 to test it. So I guess it is better not to distribute 64bit libusb-win32 driver. -- Xiaofan http://mcuee.blogspot.com _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
