Dmitry Torokhov wrote:
On 3/27/07, Chuck Ebbert <[EMAIL PROTECTED]> wrote:
Dmitry Torokhov wrote:
>>
>> And why did the mouse numbers all get rearranged in 2.6.20, e.g.
>> mouse1 became mouse2 for many people?
>
> Input devices are not guaranteed to be stable.
>
So people with z-axis mice need to redo their X config for each
kernel release when the device numbers change? Or should they
be using some other configuration?
People using this now have X crashes on kernel upgrade because
event1 became event2:
Driver "evdev"
Option "Device" "/dev/input/event1"
I'd recommend matching on "phys" or individual capabilities bits
instead of device node. See "man evdev".
I wrote a few udev rules to create specific /dev nodes for X with evedv
(I run with multiple X users / screens / keyboards / mice on one
machine). I can forward you the udev rules and helper scripts if you
want. This means that you can hardcode the /dev nodes in your xorg.conf
file and udev will make sure they don't move on you. I wrote this up in
the early days of evdev development before the phys stuff was there.
Matt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
