Martin Pitt [2009-11-30 10:57 +0100]:
> Questions:
>
> * Should we maintain this in udev proper, in extras/input_id/ ? (My
> preferred solution, since it's not really X.org specific). I'm up
> for maintaining it.
I discussed that on IRC with Kay today, and committed this to udev
trunk now.
> * Should udev itself install rules which call this, or should we just
> provide it for other packages to use? Calling it in udev itself
> feels a little more robust to me, but it would mean that the
> probing would be done in vain on systems which use X.org with hal.
It is in udev itself now, since it also helped to clean up
/lib/udev/rules.d/60-persistent-input.rules (look at the nice joystick
detection rule...).
I also made the following changes compared to the version of the
original mail:
* Works on "eventN" (and similar) devices now, not on the parent
"inputN" device. This is where you usually need them (in
60-persistent-input.rules as well as X.org)
* Argument should not specify /sys/ prefix any more, to be consistent
to other probers, and for just using "input_id %p"
With those, the xorg rules do not need to jump through hoops to grab
the parent device's properties any more, and can just say
ENV{ID_INPUT_KEY}=="*?", IMPORT{file}="/etc/default/keyboard"
or
ENV{ID_INPUT_TOUCHPAD}=="1", ENV{x11_driver}="synaptics"
(The latter won't be used literally, since we still have some quirks,
but the structure is still easier than in the originally announced
rules.)
So now this needs to trickle into the distros, before X.org can rely
on it.
Martin
--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
Attachment:
signature.asc
Description: Digital signature
