On Mon, Apr 27, 2009 at 00:31, Phil Endecott <phil_cmcsb_endec...@chezphil.org> wrote: > 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?
These links got added to distinguish multiple keyboards on mainframe-like servers, that's why the rules have been so strict so far, and cover only "real" input devices. :) We see several mouse-like devices, which are not covered by that, and we might need to find a scheme to include them in the link creation. We need to be careful here though, because there are tons of HID devices with "00" which have nothing to do with input devices in the usual sense. I have a thermometer which is exactly like that. :) What kind of kernel devices does this device create, I mean, if you run "udevadm monitor --kernel" and plug it in, what does it say? Care to show the entire sequence? Is it "inputX" only for the input devices, or do you get also a "mouseX" device? Also, care to add the full section of "lsusb -v" for this device? Thanks, Kay -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
