Hi Xiaofan, >> I would be curious to know, whether you see some principial issue with >> the suggested approach of simply assigning the same backend to all of >> the interfaces from the IAD, based on the knowledge that Windows always >> puts them under responsibility of the same driver. As mentioned before, >> in my tests that worked, but of course I need to admit that the tests >> included just limited set of operations interesting for my use case. > > I tend to agree with you that this should work. But I have to admit > that I am not a programmer myself and do not quite know all the > internals of libusbx. Pete is the main Windows developer for libusbx > and he is the one to depend on unless someone else jumps in to > help.
Thanks, understood. >>From what I see, usually IAD is used for Video/Audio device and > also USB Composite device which includes CDC (eg: CDC-ACM) > as one of the function. What is your device? The use case mentioned targets devices implementing the "new" USB3 Vision industrial standard http://www.visiononline.org/vision-standards-details.cfm?type=11 The USB3 Vision functinality of the device is accessible through set of 1-3 (in current version) interfaces associated through the IAD. The device may, however, provide also other interfaces, possibly unrelated to USB3 Vision. 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
