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. Best regards, Michael -----Ursprüngliche Nachricht----- Von: Xiaofan Chen [mailto:xiaof...@gmail.com] Gesendet: Sonntag, 21. Juni 2009 12:46 An: Michael Fischer Cc: Freddie Chopin; openocd-development Betreff: Re: [Openocd-development] Will the next release 0.2.0 build on FTD2XX support? On Sun, Jun 21, 2009 at 6:38 PM, Xiaofan Chen<xiaof...@gmail.com> wrote: > On Sun, Jun 21, 2009 at 6:33 PM, Michael Fischer<fische...@t-online.de> wrote: >> if the installer support more than FT2232 device, it must install >> all the driver this way. I think it is not a good idea, and the >> user should point to the directory where the driver exist. >> Like the normal way of installing driver. >> > > I see what you mean. Unfortunately this is sometimes the > only way to install the libusb-win32 device driver based on > my past experience. Windows will favor the existing > WHQL based FTDI driver and refused to install the > non-certified libusb-win32 driver. > > This is part of the complication of using libusb-win32 and > libftdi under Windows. I agree with Freddie, FDT2xx is the > nature choices for Windows user. The solution can be to build a binary package to automatically do this. libusb-win32 has an example of using NSIS. It is also possible to use other open source installers. http://libusb-win32.svn.sourceforge.net/viewvc/libusb-win32/trunk/libusb/exa mples/ http://nsis.sourceforge.net/Main_Page -- Xiaofan http://mcuee.blogspot.com _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
