Re: Lost keypresses [was Re: GGI and cli/sti in X]

Geert Uytterhoeven (Geert.Uytterhoeven@cs.kuleuven.ac.be)
Wed, 1 Apr 1998 13:42:51 +0200 (CEST)

On 1 Apr 1998, Andreas Schwab wrote:
> Geert Uytterhoeven <Geert.Uytterhoeven@cs.kuleuven.ac.be> writes:
> |> However, now I switched to a PS/2 keyboard on my CHRP box (which has both ADB
> |> and PS/2 keyboard connectors), and now X has problems with the scancode
> |> prefixes. It just ignores the 0xe0 (unknown key) and interpretes the next
> |> scancode. For e.g. cursor up, this means I get a KP_2, since the scancodes for
> |> cursor up are 0xe0 followed by the scancode for KP_2.
>
> But on Intel you'll get the prefixes as well, don't you? So why does it
> work there?

On Intel, they use different code. Look for the ASSUME_CUSTOM_KEYCODES define
in xc/programs/Xserver/hw/xfree86/common/xf86KbdLnx.c. XF68_FBDev assumes you
have a sane keyboard system without prefixes.

> |> 1. Will it work if I change the keyboard mode from VC_RAW to VC_MEDIUMRAW?
> |> AFAIK the only difference is that VC_MEDIUMRAW sends single keycodes,
> |> while VC_RAW sends scancodes, which may be prefixed. I haven't tried it
> |> yet, though.
>
> |> 2. Is there a good reason for keeping the scancode system? Life would be
> |> much easier if each key would generate a unique single keycode.
> |> (preferably even 16 bit, since 8 bit (7 bit plus up/down bit) is too
> |> limited for some keyboards)
>
> IMHO these questions should be solved once and for all architectures.

If VC_MEDIUMRAW won't work, I don't know how to have a single binary on PPC
that will work with both ADB and PS/2 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