> Is this ...?
Oi.
Here we have bInterfaceSubClass = xFF.
That's this device TELLING US THIS DEVICE DOES NOT TALK SCSI.
We shouldn't be surprised to discover this device then indeed does not
talk SCSI?
How about we blacklist all the bInterfaceSubClass that Windows does not
regard as generic. I remember Windows does regard bInterfaceSubClass =
x06 as generic. I think I remember there are two others. Please stay
tuned for a moment. Meanwhile,
> ...
At length ...
This device does NOT describe itself as generic e.g. not much like x 08
06 50 = MassStorage SCSI BBB.
We may not even have the Windows CBI/CB driver here?
Are we observing a Windows driver from a vendor other than Microsoft?
I see:
bDeviceClass : 0x00 (0)
bDeviceSubClass : 0x00 (0)
bDeviceProtocol : 0x00 (0)
...
InterfaceNumber: 0x00
...
Class = 0x34
SubClass = 0x6d
Protocol = 0x37
...
InterfaceNumber: 0x00
...
Class = 0x08
SubClass = 0xff
Protocol = 0x01
I'm guessing that SubClass lines means we have bInterfaceClass
...SubClass ...Protocol = x 08 FF 01.
Pat LaVarre
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
|
