Initial testing of your patch indicates that this seems to fail for both
composite and driverless devices. Composite seems to be due to not processing
the usbccgpp, but its children, and driverless seems to be due to driverless
devices not providing a software key/driver key in the first place (which
indeed is confirmed by our existing message `The following device has no
driver, libusb will not be able to access it`, which is only triggered if the
driver key was not found)...
/Pete
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/147#issuecomment-34943935
------------------------------------------------------------------------------
Android apps run on BlackBerry 10
Introducing the new BlackBerry 10.2.1 Runtime for Android apps.
Now with support for Jelly Bean, Bluetooth, Mapview and more.
Get your Android app in front of a whole new audience. Start now.
http://pubads.g.doubleclick.net/gampad/clk?id=124407151&iu=/4140/ostg.clktrk
_______________________________________________
libusbx-devel mailing list
libusbx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusbx-devel
