On Fri, Dec 30, 2016 at 1:12 AM, Paul Fertser <[email protected]> wrote: > Hi, > > On Thu, Dec 29, 2016 at 09:30:22PM +0800, Xiaofan Chen wrote: >> With the release of libusb-1.0.21, the other option may be to use >> usbdk Windows backend. usbdk is an open source driver (Apache >> 2.0License). > > This looks like a very interesting option, would be rather welcomed by > J-Link windows users!
Yes. > Is libusb DLL built for usbdk binary compatible with the one built for > WinUSB? You can build the DLL which support both. The following configure option will do that. Probably in the future release the default will be set to "yes" --enable-usbdk use UsbDk Windows backend [default=no] > Regarding USB filter drivers, I've heard negative feedback about the > concept itself, people claim they were having hell of a time trying to > remove libusb-win32 filters from the system when something went > wrong. The very concept seems too invasive and architecturally wrong, > hence fragile. Damn you microsoft, why not just provide any sane API?! Actually filter drivers targeting specific device are quite okay. libusb-win32 filter (0.1.12.2 or earlier) was really problematic. But with the release of 1.2.x we have not got really negative reviews. 1.2.6.0 is the latest version of libusb-win32 and it was released on 17-Jan-2012, almost five year ago. The major problem with 0.1.12.2 or earlier version is that it tried to be the filter of all class of USB device and that proved to be really problematic and will cause all kinds of problems including BSOD or lost of functions of keyboard/mouse/etc. libusb-win32 1.2.6.0 provided the GUI which only filters for specific device. It still has the option to filter for all possible class of USB device through the command line for those who want to mess their system. :) BTW, libusb-win32 inf wizard no longer works for newer systems and it is depreciated and we recommend Zadig or libusbK inf-wizard. usbdk is the same, it provides filter for user specified USB device like J-Link or FTDI device. > BTW, I've noticed that the official libusb releases directory [1] > lacks 1.0.21 even though it was apparently released more than a month > ago. > > [1] https://sourceforge.net/projects/libusb/files/libusb-1.0/ Yes I know this. I will check with the other maintainers on this issue. -- Xiaofan ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
