From: Krzysztof Halasa <khc@pm.waw.pl>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: 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: Thu, 15 Feb 2007 01:06:40 +0100 [thread overview]
Message-ID: <m34ppojncf.fsf@maximus.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.61.0702142257490.19368@yvahk01.tjqt.qr> (Jan Engelhardt's message of "Wed, 14 Feb 2007 22:58:42 +0100 (MET)")
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.
--
Krzysztof Halasa
next prev parent reply other threads:[~2007-02-15 0:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-14 18:56 Linus' laptop and Num lock status 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 [this message]
2007-02-20 13:57 ` Helge Hafting
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=m34ppojncf.fsf@maximus.localdomain \
--to=khc@pm.waw.pl \
--cc=dax@gurulabs.com \
--cc=jengelh@linux01.gwdg.de \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.