i386 AT keyboard LED question.

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?

Thanks,

Nick
-- 
"Person who say it cannot be done should not interrupt person doing it."
-Chinese Proverb
-
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: i386 AT keyboard LED question.
    • From: Vojtech Pavlik <[email protected]>

• Prev by Date: Re: (pspace,pid) vs true pid virtualization
• Next by Date: Re: 2.6.16-rc4-mm1
• Previous by thread: [PATCH] tg3: netif_carrier_off runs too early; could still be queued when init fails
• Next by thread: Re: i386 AT keyboard LED question.
• 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]