On Mon, Feb 20, 2006 at 08:03:26PM +0000, Nick Warne wrote:
> Hi Vojtech,
>
> I wondered why numlock LED goes off during boot process, even though I ask
> BIOS to turn on;
>
> atkbd.c
>
> /*
> * If the get ID command failed, we check if we can at least set the LEDs on
> * the keyboard. This should work on every keyboard out there. It also turns
> * the LEDs off, which we want anyway.
> */
> param[0] = 0;
> if (ps2_command(ps2dev, param, ATKBD_CMD_SETLEDS))
> return -1;
>
>
> What is the rationale *why* we want LEDS off anyway?
Some old notebooks forget them on, which makes the keyboard unusable -
you get '4' instead of 'u', etc.
We can't read the LED state anyway (except for going to the BIOS data
structures, which isn't reasonable from the atkbd driver), and we need
to initialize it, so off is the safer default.
Further, this has been the behavior of Linux since it was first
implemented, and thus, in my rewrite of the keyboard handling, I didn't
change it.
It's trivial to change the default lock state in init scripts / xdm
config / X config, too.
--
Vojtech Pavlik
Director SuSE Labs
-
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/
[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]
