From: Xiaofan C. <xia...@gm...> - 2010-01-14 23:22:19
|
On Fri, Jan 15, 2010 at 4:25 AM, Michael Plante <mic...@gm...> wrote: > libusb-win32 took over the "USB Composite Device", not the MI* devices, and > those MI* devices (channels A&B) disappeared at that point. The latest version of libusb-win32, 0.1.12.2, should support both method, you can use it to take over the whole USB composite device, or use it to bind to individual interface. This has been verified by the OpenOCD project when using the libusb-win32 device driver instead of the closed source ftd2xx driver. > WinUSB, at > least presently, seems to be doing things more like the closed-source ftd2xx > drivers did, by leaving the composite device alone and installing twice, > once for each MI*. Can WinUSB do it the other way, too, and, if so, is > there a reason to prefer one particular method? > I believe WinUSB is more interface oriented. -- Xiaofan http://mcuee.blogspot.com |