Detecting the used keyboard driver

[Peter Hutterer]

On Mon, May 04, 2009 at 11:09:31AM +0200, Gregory Smirnov wrote:
> 2009/5/3 Matthew Garrett <mjg59 at srcf.ucam.org>
> 
> > On Sun, May 03, 2009 at 08:00:28PM +0200, Marvin Raaijmakers wrote:
> > > Yes I know the kernel keycode to X keycode translation is fixed for
> > > each keyboard driver. But the problem is that the evdev driver (in the
> > > X server) does another translation than the kbd driver. You stated:
> > >  "As long as the kernel keycode is KEY_BATTERY, the X keycode will
> > > depend only on whether kbd or evdev is in use."
> > > And now we've come to the main question in my first mail: how can i
> > > detect whether the X server uses the evdev or kbd driver?
> >
> > Like I said, don't. Add the kbd keycodes to the pc105 keymap.
> >
> >
> 
> Hello, I use program that depends on X keycodes as well and have the same
> problem.
> What do you mean "Add the kbd keycodes to the pc105 keymap"? Keycodes are
> already present but has completely different meaning. Like in xkb key
> "cursor arrow up" has the same keycode as "print screen" in evdev. Evdev is
> suceeder of xkb, why *some* keycodes has just changed without an option to
> check the system for compatibility?

there's nothing wrong with evdev's keymap, only with clients that don't update
the keytables correctly.

Cheers,
  Peter