Re: keyboard.h

Geert Uytterhoeven (geert@geert.cs.kuleuven.ac.be)
Sun, 6 Dec 1998 16:25:00 +0100 (MET)

On Sat, 5 Dec 1998, Paul Barton-Davis wrote:
> Well, almost. The problem is that X has its own set of
> scancode/keycode mappings, and in order to look up the kernel mapping,
> it has to translate from its "AT Keycodes" to the Linux equivalent
> (and then back again at the keysym level). So there is an array in
> xf86KbdLnx.c called at2lnx which does this mapping, and *it* has to
> have the kernel keycodes that correspond to X's view of the world.
> This is pretty ugly, since X can choose only one such mapping. The
> existing X server define ASSUME_CUSTOM_KEYCODES is an attempt to get
> around this, but has its own problems in terms of backwards compatibility.

I added ASSUME_CUSTOM_KEYCODES to make it work with Linux/m68k. M68k boxes
don't use PC keyboards. Combined with the use of MEDIUMRAW instead of RAW
keycodes, this gives you an X server that works out-of-the-box with all kinds
of keyboards: if the kernel knows the keymap, it works :-)
(verified with Amiga, Atari, Mac, Apollo, HP300, PowerMac and even PC
keyboards).

Greetings,

Geert

--
Geert Uytterhoeven                     Geert.Uytterhoeven@cs.kuleuven.ac.be
Wavelets, Linux/{m68k~Amiga,PPC~CHRP}  http://www.cs.kuleuven.ac.be/~geert/
Department of Computer Science -- Katholieke Universiteit Leuven -- Belgium




-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/