On Mon, Apr 27, 2009 at 01:47, Phil Endecott
<phil_cmcsb_endec...@chezphil.org> wrote:
> Kay Sievers wrote:
>> 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. :)
>
> Hmm, OK; so how am I supposed to identify things that may be connected to
> different sockets and enumerated in different orders each time I use them?

Oh, it's just where it comes from, because you asked if it was intentional.

>> 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. :)
>
> Right.  I have a Wi-Spy which I think is a HID device.  Does it do any harm
> to add links for things like that?

In this case the input layer should not pick these up, so we would not
create a link here, as we hook into input events here. It's just that
we should be careful not to add stuff here which we don't really know
where it belongs, It's hard to change these links later, when people
already use them.

>> 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?
> UEVENT[1240788686.325203] add      /class/input/input15/event12 (input)

>> Care to show the entire sequence?
>
> Not sure what you mean.

The above sequence of events you posted.

>> Is it "inputX" only for the input devices, or do you get also a "mouseX"
>> device?
>
> I get only an eventX device:

Ok, so we don't get any other specific class device from the input layer.

>> Also, care to add the full section of "lsusb -v" for this device?
>
> Bus 001 Device 009: ID 077d:0410 Griffin Technology PowerMate

The device also does not tell us anything interesting.

Does the input subsystem tell us anything specific we might want to
use to classify the device? What does:
  grep . /sys/class/input/inputX/capabilities/*
print? Replace the X with the actual number, which changes with every reconnect.

Thanks,
Kay



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to