|> 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.
It seems like this assumption was wrong....
Andreas.
-- Andreas Schwab "And now for something schwab@issan.informatik.uni-dortmund.de completely different" schwab@gnu.org- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu