On Mon, Jun 24, 2013 at 7:17 PM, Paul Fertser <[email protected]> wrote: > I think I'm starting to understand what you mean (finally :)). > > My idea was that a typical OpenOCD user shouldn't be bothered to > install different drivers for different kind of adapters and that the > procedure can be made unambiguous by telling them all to just use > WinUSB, with OpenOCD using the compat layer when necessary. So using > windows would be almost as smooth as using GNU/Linux (where the user > just runs OpenOCD and doesn't care about the drivers at all, > everything handled transparently).
For Windows, you will have to deal with driver switching since in most cases, then vendor driver is not based on WinUSB. > But now you tell me that some shit-vendors tools do not work with > WinUSB so if an OpenOCD user wants to run the vendor tool he is just > forced to use vendor driver so he needs the filter mode, so he needs > libusb-win32, so he can't just use > > "OpenOCD->libusb-compat-0.1->libusbx->libusb-win32" > > because currently libusbx doesn't fully support composite devices when > using libusb-win32, so OpenOCD can't be built with libusb-compat-0.1 > because it'll be impossible to use those adapters with vendors > drivers, right? Using filter driver is convenient for some users. But if the user is not using the tools based on vendor drivers (say IAR, Keil, etc) and only OpenOCD, it is okay to switch driver to WinUSB. Even for those who want to use vendor tools and OpenOCD (with WinUSB driver), it is a hassle to switch drivers but not really that difficult either. > Moreover, have you seen my commit > 6be2a55bde5531de9897fd844c6db13e49213ae8? For the usual Windows builds > it'll make jlink, osbdm, opendous and aice use libusb-1.x api (via the > common layer inside OpenOCD), so do you mean it'll break the > functionality for those who are using e.g. jlink with old vendor's > drivers? What can be done about it? No it should not really break things. For single interface device, libusb-win32 filter seems to work fine with libusbx as well. And for those who want to use WinUSB, it is still possible to do driver switching. > Oh my, is it really such a mess? Windows driver installation for OpenOCD has always been an issue and the users seem to be able to deal with it. I can understand the confusions, but I think things can be cleared up with some documentation or wiki pages to help the end users. -- Xiaofan ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
