Hi list, I'm having a device here, that amongst others, features some descriptors within the configuration descriptor, that are not explicitely available via the libusbx API. These are:
- Interface Association Descriptor - Device Class Specific Descriptors - Super Speed Companion Descriptor While I can, for instance, read the IAD via the "extra" field, I can't do arbitrary reads - as it looks. If I consider the memory contiguous, it will fail. So I'm unable to parse anything that's not been wrapped by libusbx, like my Device Class Specific Descriptors. Though the IAD is living directly after the 8 byte configuration descriptor head in the config descriptor (within the device), the address of "extra" is nearly 7k away from its end. If the configuration descriptor would be contiguous, it would easily be possible to parse the descriptor. Am I missing something? If not, would you be willing to change this, as it would enable a lot more applications with libusbX. Thanks in advance, /Markus ------------------------------------------------------------------------------ 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
