On Sat, Jan 12, 2008 at 05:53:42PM +0000, Patrick Georgi wrote: > Hi, > > second installement of my mini-series: > > The AT keyboard driver assumes that the keyboard is set to scancode set > #1. It seems like many keyboards use set #2 (or even #3) by default now, > and some 8042-emulating chipsets don't enable translation (to #1) by > default. The BIOS then enables it to support the legacy compatibility the > PC architecture is famous for - but CoreBoot doesn't. > > http://osdever.net/ has some information on programming the 8042 (without > BIOS calls), incl. how to configure the scancode set you want to have. > > Also, 0x01 is the scancode for ESC. I didn't look if there's a special > case for escapes, but a simple "\e" instead of "\0" at that code point > might help.
Is there a way to reproduce this problem without specific hardware? (with qemu or so) -- Robert Millan <GPLv2> I know my rights; I want my phone call! <DRM> What use is a phone call, if you are unable to speak? (as seen on /.) _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel
