Tim Roberts wrote:
> You can write to the device's control endpoint
> without claiming an interface at all.
I'm not sure this is true with WinUSB on Windows.
//Peter
--
Everyone hates slow websites. So do we.
Make your
g...@novadsp.com wrote:
> 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
>
g...@novadsp.com wrote:
> Interfaces: 2
..
> Interface Number: 0
> Number of endpoints: 2
..
> 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_ERRO
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
> expec
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
