On Tue, 27 May 2003, Geert Uytterhoeven wrote: > > Hmm, as I've understood that's a 2.4-only problem as 2.5 has it solved > > differently. And I do think the translation really belong to the drivers > > that use it -- why can't it be included with the USB keyboard driver or as > > a library file? Why an unrelated driver has to be cluttered? > > It's not really used by a driver, but by the input subsystem itself. You could > add the translation to drivers/char/keyboard.c, but then it will break if you > use both the input subsystem (e.g. USB keyboard) and some other non-PS/2 > keyboard driver. I don't understand -- the scancode mapping is specific to a keyboard type. Both PC/AT and USB keyboards may use the same scancodes by chance, but others have different ones. So how can the input subsystem need a PC/AT specific mapping? Adding the table to drivers/char/keyboard.c certainly makes no sense as the file is meant to be generic. BTW, the PS/2 mapping is yet different and doesn't use prefixes. -- + Maciej W. Rozycki, Technical University of Gdansk, Poland + +--------------------------------------------------------------+ + e-mail: macro@ds2.pg.gda.pl, PGP key available +
