[PATCH] Add configuration option for use of SIGIO handlers for input events
daniel at fooishbar.org
Tue Oct 6 08:33:17 PDT 2009
On Tue, Oct 06, 2009 at 03:22:02PM +0100, Nix wrote:
> On 13 Sep 2009, Peter Hutterer spake thusly:
> > I still see configurations with AllowEmptyInput off because there was a
> > brief period when that fixed a certain broken setup. Now people use it
> > because they read it somewhere and thought it's a good idea.
> Actually I use it because with it off my keyboard is ignored unless HAL
> is running, even as of X.org 1.6.x, and HAL is an unreliable POS which
> failed to start for *years* for me, so I am reluctant to rely on it for
Have you got the relevant FDI files installed? Does lshal | grep x11,
> It's not all cargo-culting, unless you consider 'keyboard doesn't work,
> turn this option on and now it does' to be cargo-culting.
> (Note that this may have changed since 1.6.2, when I tried it last, but
> I doubt it's changed much since then.)
It should work just fine with both 1.6.2 and master.
> (As an side, this is all with kbd+mouse. I have never managed to coerce
> evdev into working at all, so I'm using kbd because, well, it doesn't
> seem to have any disadvantages. Maybe it can't deal with some key or
> other that my keyboard doesn't even have. Maybe it's not good at dealing
> with massive multilingualism, but I'm a monoglot. I don't know why you
> push evdev so hard: kbd just works on every platform I've ever tried it
> on, while evdev is an OS-specific thing requiring an off-by-default
> kernel option to be turned on and I stll haven't managed to get working
> even then. Maybe it needs some device permission to be tweaked from the
> default as well, I don't know, it doesn't log it, and I don't much care
> because, well, kbd works.)
There are many well-documented reasons to use evdev, which I won't
rehash in depth, but among them are the ability to address keyboards
independently, including different layouts for each, extended keycode
support, not having to use the TTY layer (kbd is unbelievably fragile
and complex), etc, etc.
If your setup doesn't work at all, having followed the instructions for
doing so that Peter posted quite a while back, please file bugs and
we'll fix the evdev driver if it is in any way deficient.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 197 bytes
Desc: not available
Url : http://lists.x.org/archives/xorg-devel/attachments/20091007/bf5bdf15/attachment.pgp
More information about the xorg-devel