From: Tor Arvid Lund <tor.arvid.lund@idi.ntnu.no>
To: linux-kernel@vger.kernel.org
Subject: Keyboard problem in 2.6.1
Date: Sun, 11 Jan 2004 14:08:54 +0100 [thread overview]
Message-ID: <40014AE6.3070106@idi.ntnu.no> (raw)
Hello. Upgrading from 2.6.0 to 2.6.1 gave me the problem that my
apostrophe/asterisk key didn't work (norwegian kbd layout, connected via
USB). That is, I press the key, and nothing happens. The showkey program
tells me this key has keycode 84.
So I check the patch file, and find that in the file:
drivers/char/keyboard.c
and the section:
static unsigned short x86_keycodes[256] =
the line:
- 80, 81, 82, 83, 43, 85, 86, 87, 88,115,119,120,121,375,123, 90,
^^
was changed to:
+ 80, 81, 82, 83, 84, 93, 86, 87, 88, 94, 95, 85,259,375,260, 90,
^^
Now, I am nowhere near a kernel hacker, but I thought I'd try and change
84 back to 43 (of course without any good reason other than "let's see
what happens"), and it seemed to work.
I don't know what this means, but I thought maybe that some of you who
actually _know_ a thing or two about the kernel could make something of
all of this...
PS: please CC replies to <tor.arvid.lund at idi.ntnu.no>, as I am not
subscribed to the list
Regards,
Tor Arvid
reply other threads:[~2004-01-11 13:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=40014AE6.3070106@idi.ntnu.no \
--to=tor.arvid.lund@idi.ntnu.no \
--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