From: xsdg <xsdg@freenode.org>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test1, -test4 control key "stuck"
Date: Mon, 15 Sep 2003 20:55:46 +0000 [thread overview]
Message-ID: <20030915205546.GA12833@perl> (raw)
In-Reply-To: <20030915110028.B957@pclin040.win.tue.nl>
[-- Attachment #1: Type: text/plain, Size: 1181 bytes --]
On Mon, Sep 15, 2003 at 11:00:28AM +0200, Andries Brouwer wrote:
::snip? SNIP!::
> Apparently your keyboard has problems handling the situation where many
> keys are down simultaneously.
What would happen if the kernel received two keypress events, and then one key-
release event for a single key? I'd imagine that it'd disregard the duplicate
keypress
>
> No kernel problem here - just a confusing message.
::snip? SNIP!::
any idea what might cause the key sticking problem? I wouldn't think it's
a directly hardware-related problem (though it might be in BIOS firmware, I
suppose) because the problem is resolved when I reboot.
Also, I'm not sure how the final issue I described could have occurred, since
it appears to be keymap-related. Is there some special keycode that might be
able to cause a change in the keymap? Also, does the behavior I described
match any common keymaps? I typically don't set LANG or any of the other
locale-defining variables.
> Andries
>
--
| Why do people with closed minds always open their |
| mouths? |
) http://www.cuodan.net/~xsdg/ xsdg@freenode.org (
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-09-15 20:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-15 0:04 2.6.0-test1, -test4 control key "stuck" xsdg
2003-09-15 9:00 ` Andries Brouwer
2003-09-15 20:55 ` xsdg [this message]
2003-09-15 21:28 ` Andries Brouwer
2003-09-15 23:02 ` xsdg
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=20030915205546.GA12833@perl \
--to=xsdg@freenode.org \
--cc=aebr@win.tue.nl \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox