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

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.

	-hpa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [PATCH] Use BIOS Keyboard variable to set Numlock
    • From: Bodo Eggert <[email protected]>

• References:
  • [PATCH] Use BIOS Keyboard variable to set Numlock
    • From: Bodo Eggert <[email protected]>
  • Re: [PATCH] Use BIOS Keyboard variable to set Numlock
    • From: "H. Peter Anvin" <[email protected]>
  • Re: [PATCH] Use BIOS Keyboard variable to set Numlock
    • From: Bodo Eggert <[email protected]>

• Prev by Date: Re: [PATCH 05/11] security: revalidate rw permissions for sys_splice and sys_vmsplice
• Next by Date: Re: lguest, Re: -mm merge plans for 2.6.23
• Previous by thread: Re: [PATCH] Use BIOS Keyboard variable to set Numlock
• Next by thread: Re: [PATCH] Use BIOS Keyboard variable to set Numlock
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]