Pete Batard wrote: > On 2013.04.08 19:12, Tim Roberts wrote: >> For example, in this snippet: >>> Opening device 0403:CFF8... >>> libusbx: error [init_device] device >>> '\\.\USB#VID_0403&PID_CFF8&MI_01#6&222886B8& >>> 0&0001' is no longer connected! >> the "MI_01" implies that you have a separate driver for each interface. >> In that case, I don't understand the log entries about claiming >> interface 0 and interface 1. > That's just how xusb is set [1]. It'll always try to claim all > interfaces.
Yes, but if this is a driver matching MI_01, then there will only be one interface, numbered 0. The usbccgp driver, which owns the composite device, rewrites the configuration descriptor. When the MI_01 driver goes to read the configuration descriptor, it will only contain interface 0 (which is really interface 1). The other interface will simply not appear. That's my confusion. If libusbx has (also) claimed the composite device, then I believe this. If not, then it shouldn't be possible for the MI_01 driver to learn or access the other interfaces. -- Tim Roberts, t...@probo.com Providenza & Boekelheide, Inc. ------------------------------------------------------------------------------ Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
