On Aug 16, 2013, at 1:14 PM, Jan Becvar <j...@groget.org> wrote: > > I wonder if this fully applies from the libusbx point of view. > > My understanding of its interface (but please mind my so far limited > experience with the library) was that it enumerates really the > "physical" devices, even if composite. I.e. the composite device is > still enumerated as single device with multiple interfaces rather than > multiple devices "invented" by usbccgp.sys. Am I wrong?
Unless I missed a staff meeting, libusbx can be used in either mode -- either matching the composite device (meaning all interfaces) or matching one of the interfaces. If you match the composite device, then you get the entire configuration descriptor, including the IADs. > Also, the config descriptor seems to be queried through the parent hub's > driver using IOCTL_USB_GET_DESCRIPTOR_FROM_NODE_CONNECTION thus > bypassing usbccgp.sys or any other driver associated with the composite > parent. Hmm. That would, in fact, bypass the composite parent rewriting. -- Tim Roberts, t...@probo.com Providenza & Boekelheide, Inc. ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
