On Fri, 19 Oct 2012, g...@novadsp.com wrote: > As suggested by Xiaofan firmware has two interfaces, with the second > exposing no data endpoints of its own. > > Opening the device using libusb_open_device_with_vid_pid > and then enumerating the device using libusbx functions gets me the > expected: > > ProductID: 0xA00A > Interfaces: 2 > Number of alternate settings: 1 > Interface Number: 0 > Number of endpoints: 2 > Descriptor Type: 5 > EP Address: 133 > Descriptor Type: 5 > EP Address: 6 > Number of alternate settings: 1 > Interface Number: 1 > Number of endpoints: 0 > > What I don't get is how to write to the second interface. > > Using anything other than an index of 1 for libusb_claim_interface() > returns LIBUSB_ERROR_NOT_SUPPORTED.
The first interface is index 0, the second is index 1. > I'm missing something crashingly obvious - can anyone point out what? Alan Stern ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
