Re: Bug#85629: keymap for RiscPC

[Andries.Brouwer@cwi.nl]

Russell King (rmk@arm.linux.org.uk) wrote:

    Andries.Brouwer@cwi.nl writes:
    > You mean that the hardware is the same but the initialization
    > sets one up in scancode set 1 and the other in scancode set 2?

    The keyboard hardware is the same, but what is at the end of the
    keyboard cable in the machine is different.  On a PC, the i8042
    does the conversion from whatever the keyboard is using to whatever
    the system software wants.  We don't have this layer.

Good. We are saying the same.

Quoting  http://www.win.tue.nl/~aeb/linux/kbd/scancodes-4.html :
"The usual PC keyboards are capable of producing three sets of scancodes.
... Set 1 contains the values that the XT keyboard (with only one set of
scancodes) produced, with extensions for new keys.
Someone decided that another numbering was more logical and invented
scancode Set 2. However, it was realized that new scancodes would break
old programs, so the keyboard output was fed to a 8042 microprocessor
on the motherboard that could translate Set 2 back into Set 1.
Indeed a smart construction. This is the default today.
Finally there is the PS/2 version, Set 3, used by nobody."

So, if we make the translation table act like the i8042
the result will be PC scancodes and all PC keymaps will work.

And Vojtech has input patches where he in fact uses the untranslated
values for the PC, so this translation table can also go away again.

2.5 will start soon I suppose.
Would you object against now [until Vojtech's patches are applied]
switching to PC keycodes here (in 2.5)?

Andries