LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Helge Hafting <helge.hafting@aitel.hist.no>
To: Krzysztof Halasa <khc@pm.waw.pl>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
	Dax Kelson <dax@gurulabs.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Jean Delvare <khali@linux-fr.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Linus' laptop and Num lock status
Date: Tue, 20 Feb 2007 14:57:01 +0100	[thread overview]
Message-ID: <45DAFE2D.3060606@aitel.hist.no> (raw)
In-Reply-To: <m34ppojncf.fsf@maximus.localdomain>

Krzysztof Halasa wrote:
> Jan Engelhardt <jengelh@linux01.gwdg.de> writes:
>
>   
>>> I checked, and looking at offset 0x497 seems to work fine on a couple of
>>> systems with USB keyboards.
>>>       
>> Probably just because legacy mode was enabled. Plus I wonder what 0x497 will
>> return when there is actually more than one USB keyboard connected at boot.
>>     
>
> I bet all would share LED states. If you can use multiple keyboards
> in legacy mode at all, of course.
>   
I have used multiple keyboards, for a 2-user machine.

The bios interact with only one of the keyboards, and track LED state on 
that.
Other keyboard(s) become useful once the linux comes up with
its event interface. You then have one set of LEDS per keyboard.

Helge Hafting

  reply	other threads:[~2007-02-20 14:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-14 18:56 Dax Kelson
2007-02-14 19:12 ` Linus Torvalds
2007-02-14 19:19   ` Dax Kelson
2007-02-14 19:21   ` Jean Delvare
2007-02-14 19:32     ` Linus Torvalds
2007-02-14 21:34       ` Dax Kelson
2007-02-14 21:58         ` Jan Engelhardt
2007-02-15  0:06           ` Krzysztof Halasa
2007-02-20 13:57             ` Helge Hafting [this message]
2007-02-15  0:31           ` Alan
2007-02-18 16:19       ` Jean Delvare
2007-02-15 14:34     ` H. Peter Anvin
2007-02-18 16:04       ` Jean Delvare
2007-02-18 17:32         ` H. Peter Anvin
2007-02-18 18:06           ` Randy Dunlap
2007-02-19  0:26             ` H. Peter Anvin
2007-02-18 17:54         ` Randy Dunlap
2007-02-14 19:26   ` Arjan van de Ven
2007-02-15 14:25   ` H. Peter Anvin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45DAFE2D.3060606@aitel.hist.no \
    --to=helge.hafting@aitel.hist.no \
    --cc=dax@gurulabs.com \
    --cc=jengelh@linux01.gwdg.de \
    --cc=khali@linux-fr.org \
    --cc=khc@pm.waw.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --subject='Re: Linus'\'' laptop and Num lock status' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).