On 13-Aug-13 16:16, Xiaofan Chen wrote: > Hmm, I am not be totally correct. I just tried one USB Web > Camera which is an IAD device, the first collection has two > interfaces (Interface count =2, Interface and Interface 1), > the second collection has two interface (Interface count =2, > Interface 2 and Interface 3), Windows indeed only show them > as two device. But Zadig is the same, it will not present them > as 4 device, but rather only two device, each corresponds > to one interface collection.
Thanks for the confirmation, I was slowly getting lost :-) My device is using a collection of up to three interfaces in the IAD, Windows/Zadig presenting the entire collection of these interfaces as a single device for driver installation. My main question is if I can install e.g. WinUSB there and use it (all those interfaces) from libusbx. (The device might present additional interfaces besides this IAD as well but those are of no interest now. I can post some more details about the device if needed, but based on your last e-mail they might be perhaps no more important...) > In this case, you should only claim Interface 0 and Interfac 2. If I claim only Interface 0 (first interface of my IAD) than I cannot use the other two interfaces of the IAD, such as read/write their endpoints. Therefore I assumed I have to claim all three interfaces. Maybe here I'm missing some part of libusbx API? From the previous e-mail: >> Finally, during my earlier experiments, I tried a trivial >> "hack"-modification of libusbx, assigning the same backend (subAPI) to >> the associated interfaces as to the first one - and after this >> modification everything "just worked", therefore I was hoping there >> would be a solution. However, due to my lack of knowledge of libusbx >> internals, I'm of course not sure if such approach might have some >> unexpected side effects. > > What do you mean by "just worked"? What is your device and > what is your goal of using libusbx? I mean that as far as I could observe, it worked in the same way as if I assigned the driver to the composite parent, i.e. I could claim and use all of the interfaces of the IAD. I did this "experiment" some time ago though, would need to check again including more thorough tests to see if there were no "surprises" around. Jan ------------------------------------------------------------------------------ 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
