From: Andries Brouwer <aebr@win.tue.nl>
To: Andries Brouwer <aebr@win.tue.nl>
Cc: Petr Vandrovec <vandrove@vc.cvut.cz>,
Zwane Mwaikambo <zwane@linuxpower.ca>,
vojtech@suse.cz, linux-kernel@vger.kernel.org
Subject: Re: Another keyboard woes with 2.6.0...
Date: Sun, 14 Sep 2003 12:34:44 +0200 [thread overview]
Message-ID: <20030914123444.D3371@pclin040.win.tue.nl> (raw)
In-Reply-To: <20030914121323.B3371@pclin040.win.tue.nl>; from aebr@win.tue.nl on Sun, Sep 14, 2003 at 12:13:23PM +0200
On Sun, Sep 14, 2003 at 12:13:23PM +0200, Andries Brouwer wrote:
> > From log it looks like that switch likes 0x41 a lot: it reports ID 0x41AB,
> > it reports current scan set 0x41, and when we enable it, it returns spurious
> > 0x41... And the last 0x41 is one which confuses everything.
>
> Yes. ID is OK. Scancode set is OK. But the final one is unexpected.
>
> You say "confuses everything".
> Is it not treated as a keypress for the F7 key?
Hmm. Yes. An F7 that is never released.
Is that what you see - an infinitely repeated F7 until
you hit the next key?
And the 0x41 is generated by this switch?
And it also occurs on 2.4 but there nothing bad happens?
next prev parent reply other threads:[~2003-09-14 10:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-12 18:33 Another keyboard woes with 2.6.0 Petr Vandrovec
2003-09-13 18:52 ` Andries Brouwer
2003-09-13 21:40 ` Petr Vandrovec
2003-09-14 10:13 ` Andries Brouwer
2003-09-14 10:34 ` Andries Brouwer [this message]
2003-09-14 19:52 ` Petr Vandrovec
2003-09-14 22:10 ` Andries Brouwer
2003-09-19 11:38 ` Vojtech Pavlik
-- strict thread matches above, loose matches on Subject: below --
2003-09-12 16:50 Petr Vandrovec
2003-09-12 17:45 ` Zwane Mwaikambo
2003-09-16 21:23 ` Andries Brouwer
2003-09-16 22:45 ` Jamie Lokier
2003-09-16 22:49 ` Zwane Mwaikambo
2003-09-16 23:12 ` Zwane Mwaikambo
2003-09-16 23:18 ` Zwane Mwaikambo
2003-09-17 0:01 ` Andries Brouwer
2003-10-06 22:08 ` Petr Vandrovec
2003-10-14 18:16 ` Petr Vandrovec
2003-10-14 21:27 ` Andries Brouwer
2003-09-13 19:06 ` Pekka Pietikainen
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=20030914123444.D3371@pclin040.win.tue.nl \
--to=aebr@win.tue.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=vandrove@vc.cvut.cz \
--cc=vojtech@suse.cz \
--cc=zwane@linuxpower.ca \
/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.