From: "James H. Cloos Jr." <cloos@jhcloos.com>
To: Ralf Hildebrandt <Ralf.Hildebrandt@charite.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test1-ac2 issues / Toshiba Laptop keyboard
Date: 17 Jul 2003 17:18:28 -0400 [thread overview]
Message-ID: <m365m0etsr.fsf@lugabout.jhcloos.org> (raw)
In-Reply-To: <20030717201039.GC25759@charite.de>
>>>>> "Ralf" == Ralf Hildebrandt <Ralf.Hildebrandt@charite.de> writes:
Ralf> atkbd.c: Unknown key (set 2, scancode 0xb2, on isa0060/serio0) pressed.
Ralf> But this happened while typing NORMALLY, with no frills :) I
Ralf> mean, I was just typing in some unix commands - so I never even
Ralf> came close to the keys I never use anyway...
Interesting.
The one example I quoted above, atkbd_set2_keycode[0xb2] is in fact 0.
Perhaps your kb is doing something unusual w/ the key release events.
If the kb is, eg, |=ing w/ 0x80 rather than preceding w/ 0xf0 then
0xb2 would be the release event for 0x32. atkbd_set2_keycode[0x32]
is 48 (KEY_B in input.h).
So if you get unknown scancode 0xb2 from hitting the B key, that is
the cause.
Otherwise, perhaps a list of some keys and what they printk()
might help debug it.
-JimC
next prev parent reply other threads:[~2003-07-17 21:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-17 14:18 2.6.0-test1-ac2 issues / Toshiba Laptop keyboard Ralf Hildebrandt
2003-07-17 14:33 ` Michael Kristensen
2003-07-17 14:36 ` Ralf Hildebrandt
2003-07-17 14:38 ` Alan Cox
2003-07-17 14:45 ` Ralf Hildebrandt
2003-07-17 18:24 ` Alvaro Lopes
2003-07-17 20:09 ` Ralf Hildebrandt
2003-07-17 18:15 ` James H. Cloos Jr.
2003-07-17 20:10 ` Ralf Hildebrandt
2003-07-17 20:40 ` Dumitru Ciobarcianu
2003-07-18 6:36 ` Ralf Hildebrandt
2003-07-18 12:45 ` Alvaro Lopes
2003-07-18 13:49 ` Ralf Hildebrandt
2003-07-17 21:18 ` James H. Cloos Jr. [this message]
2003-07-18 6:44 ` Ralf Hildebrandt
2003-07-19 13:18 ` Chris Heath
-- strict thread matches above, loose matches on Subject: below --
2003-07-17 20:55 Grover, Andrew
2003-07-18 12:43 ` Alvaro Lopes
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=m365m0etsr.fsf@lugabout.jhcloos.org \
--to=cloos@jhcloos.com \
--cc=Ralf.Hildebrandt@charite.de \
--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 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.