On Wed, Jul 3, 2013 at 5:02 PM, Julien D'ascenzio <julien.dascen...@paratronic.fr> wrote: > > When I use xusb with my product I have this message: > > Reading Extended Compat ID OS Feature Descriptor (wIndex = 0x0004): > > 00000000 28 00 00 00 00 01 04 00 01 00 00 00 00 00 00 00 > (............... > > 00000010 00 01 57 49 4e 55 53 42 00 00 00 00 00 00 00 00 > ..WINUSB........ > > 00000020 00 00 00 00 00 00 00 00 ........ > > Reading Extended Properties OS Feature Descriptor (wIndex = 0x0005): > > Failed: Pipe error > > In the source code I see that: > - Extended Compat ID is read with LIBUSB_RECIPIENT_DEVICE > > - Extended Properties OS is read with LIBUSB_RECIPIENT_INTERFACE > > When I use LIBUSB_RECIPIENT_DEVICE for read Extended Properties OS it’s ok. > > So, I’d like to, understand why LIBUSB_RECIPIENT_INTERFACE is used. >
Please refer to this thread to see if that helps. http://libusbx.1081486.n5.nabble.com/Libusbx-devel-libusbx-xusb-example-and-Microsoft-OS-Descriptor-td845.html http://www.microchip.com/forums/m707870.aspx -- Xiaofan ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
