Re: [PATCH] Use BIOS Keyboard variable to set Numlock

[Bodo Eggert]

On Wed, 11 Jul 2007, H. Peter Anvin wrote:
> Bodo Eggert wrote:

> >> That being said, one could argue that since this is a BIOS interface it
> >> should be queried via INT 16h, AH=02h and stuffed in the zeropage
> >> structure.  This would also solve the issue of it not being supported by
> >> non-BIOS firmware.
> > 
> > This is an interesting option, but it's more invasive. I'd rather like a 
> > feedback saying we can depend on that data area to be there.
> 
> I don't think we can.  You might find garbage there.

I asked you not to say that ...


Can somebody using LinuxBIOS or OpenFirmware please do

dd if=/dev/mem bs=1 count=1 skip=$((0x417)) | hexdump
 - and -
dd if=/dev/mem bs=1 count=14 skip=$((0x400)) | hexdump

You should get
 - one byte for the keyboard status, 0x20 == Numlock

 - seven words for the legacy serial and parallel ports, port address only
   (e.g. 03f8 02f8 0000 0000 0378 0000 0000)

-- 
C program run. C program crash. C programmer quit. 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/