Hello, Xiaofan, big thanks for your elaborate explanations.
On Sat, May 02, 2015 at 11:06:53AM +0800, Xiaofan Chen wrote: > I am not a programmer myself and I have not looked into the > patch in detail. But I believe there is a way to patch the > existing code without the need to replacing the TI drivers with > single WinUSB driver. It needs to list all the device associated > with the vid/pid combination and determine which is the right one > to use (eg: using bInterfaceClass) and then open that one and > claim the relevant interface (Interface 2). If that becomes the official LibUSB recommendation for all the software that uses the API to do that, the OpenOCD project will be modified accordingly. I do not think it's fair to require some special handling for windows, the libusb users need to have a uniform interface; even if it becomes ugly, it needs to be cross-platform by default. For the 0.9.0 release I'd just add more documentation to README.Windows; if the decision about the proper API usage is made, the code can be modified later. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:[email protected] ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ OpenOCD-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openocd-devel
