Markus wrote: > I'm not entirely sure if this topic belongs to this list, but as > it might affect usbK integration, it seems the best place to ask first. > > I've got a custom composite device with 3 interfaces for which I created > a usbK driver package by means of the usbK wizard (interface 0x0). > > When using libusbx, the device works as expected if I'm just accessing > interface 0, however as soon as I try to claim one of the other > interfaces, I receive an error -12 from libusb_claim_interface. > ... > Is it a misconception on my side, that it suffices to have a > driver registered for interface 0x0 of the device?
It is a misconception. With the exception of a few device classes where interfaces are grouped (like audio and video), every interface in a USB device stands alone as a separate device, and needs a separate driver. If you register a driver for the composite device (without an interface number at all), then you only need one driver. But if you don't register for the composite device, the system supplies one (usbccgp), which creates N separate subdevices, each of which starts crying for its own driver. -- Tim Roberts, t...@probo.com Providenza & Boekelheide, Inc. ------------------------------------------------------------------------------ Monitor your physical, virtual and cloud infrastructure from a single web console. Get in-depth insight into apps, servers, databases, vmware, SAP, cloud infrastructure, etc. Download 30-day Free Trial. Pricing starts from $795 for 25 servers or applications! http://p.sf.net/sfu/zoho_dev2dev_nov _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
