Hi Kay,
Sorry for the delay; the email address that I used originally for this
bug is now spam-filtered. I seem to get mountains of spam to Debian
bug addresses, for some reason. Any random string @ chezphil.org will
reach me.
SUBSYSTEMS=="usb", \
ATTRS{bInterfaceClass}=="03", ATTRS{bInterfaceProtocol}=="00", \
ENV{ID_CLASS}="misc"
I now get the desired symlinks:
/dev/input/by-id/usb-Griffin_Technology,_Inc._Griffin_PowerMate-event-misc
/dev/input/by-path/pci-0000:00:10.2-usb-0:1:1.0-event-misc
It's undefined if bInterfaceProtocol is 0.
What is the subclass value of the device? Like "lsusb -v" prints for a mouse:
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 1 Boot Interface Subclass
bInterfaceProtocol 2 Mouse
I get:
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 No Subclass
bInterfaceProtocol 0 None
By chance I have been learning about USB HID recently and I have a copy
of the spec in front of me. Apparently (sec. 4.3):
"the bInterfaceProtocol member of an Interface descriptor only has
meaning if the bInterfaceSubClass member declares that the device
supports a boot interface, otherwise it is 0."
So protocol==0 is not specific to this unusual device; even a keyboard
or mouse will have 0 for its non-boot interfaces. So the current logic
will only create /dev/by-id|path nodes for boot interfaces. Is that intentional?
Cheers, Phil.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
