> We're not doing anything fancy but sending a basic Windows IOCTL for
> that, so I'd rally with Tim in thinking that Windows may not find your
> descriptors compliant enough. And I'm ready to bet that Microsoft's
> USBView [1] will also fail reading your descriptors.
That is right, also Usbview do
Arne Pagel wrote:
> That is right, also Usbview doesn't show any Configraution Descriptors, just
> Device and Endpoints.
The fact that it shows endpoints says that, at SOME point in time, the
system was able to read your configuration descriptor. Endpoint
descriptors do not exist on their own --
On 28.11.2012 19:01, Tim Roberts wrote:
> The fact that it shows endpoints says that, at SOME point in time, the
> system was able to read your configuration descriptor. Endpoint
> descriptors do not exist on their own -- they are part of the
> configuration descriptor.
Thanks, I just thought that
On Thu, Nov 29, 2012 at 1:39 AM, Arne Pagel wrote:
> On Linux lsusb -d16d0:05be -vvv gives following, which displays the Config
> descriptor or?
> http://nopaste.info/8e45bca2da.html
Configuration Descriptor:
bLength9
bDescriptorType2
wTotalLength 3
On Thu, Nov 29, 2012 at 1:39 AM, Arne Pagel wrote:
>> We're not doing anything fancy but sending a basic Windows IOCTL for
>> that, so I'd rally with Tim in thinking that Windows may not find your
>> descriptors compliant enough. And I'm ready to bet that Microsoft's
>> USBView [1] will also fail
