[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#564258: xserver-xorg-input-evdev: evdev on accelerometers is broken



On Tue, Jan 19, 2010 at 22:31:50 +0100, Martin Pitt wrote:

> > E: SUBSYSTEM=input
> > E: ID_INPUT=1
> > E: x11_driver=evdev
> 
> I wonder which rule assigns this. At least in Ubuntu,
> /lib/udev/rules.d/65-xorg-evdev.rules looks like
> 
> -------------- 8< ------------------
> ACTION!="add|change", GOTO="xorg_evdev_end"
> 
> # By default, we use the -evdev driver for every mouse, keyboard, touchscreen
> # or touchpad; later rules can then change the driver for specific input
> # devices.
> ENV{ID_INPUT}=="", GOTO="xorg_evdev_end"
> ENV{ID_INPUT_MOUSE}=="?*", ENV{x11_driver}="evdev"
> ENV{ID_INPUT_KEY}=="?*", ENV{x11_driver}="evdev"
> ENV{ID_INPUT_TOUCHSCREEN}=="?*", ENV{x11_driver}="evdev"
> ENV{ID_INPUT_TOUCHPAD}=="?*", ENV{x11_driver}="evdev"
> 
> LABEL="xorg_evdev_end"
> -------------- 8< ------------------
> 
> I. e. it does _not_ assign evdev to any ID_INPUT device, just to
> known types. In particular, it doesn't use evdev for joysticks either,
> since the perception was that this is too confusing. Such a rule could
> be shipped by xserver-xorg-input-joystick.
> 
It looks like this because I changed it after people started reporting
this problem, and ubuntu synced it :)
See
http://git.debian.org/?p=pkg-xorg/driver/xserver-xorg-input-evdev.git;a=commitdiff;h=d293b7ae066ab55540809b99ba770174dfca3bc7

> Do you happen to have a rule which looks like
> 
>   ENV{ID_INPUT}=="?*", ENV{x11_driver}="evdev"
> 
That's pretty much what we had.

> ? If so, my recommendation would be to drop this. We don't need X.org
> to listen to obscure devices like your accelerometer or headphone
> jacks. Button-type devices like lids are already covered by
> ID_INPUT_KEY (which is not the same as _KEYBOARD, NB).
> 
Hrm.  This means with inputclasses we'll need one inputclass section for
each device type.  Or tag the devices we don't want to handle somehow in
the udev db.

Thanks for your answer,
Julien



Reply to: