From: Georg Nikodym <georgn@somanetworks.com>
To: Jan Schubert <Jan.Schubert@GMX.li>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0_test6: CONFIG_I8K produces wrong/no keycodes for special buttons
Date: Mon, 6 Oct 2003 16:00:49 -0400 [thread overview]
Message-ID: <20031006160049.6e428690.georgn@somanetworks.com> (raw)
In-Reply-To: <3F81ACB5.2000309@GMX.li>
[-- Attachment #1: Type: text/plain, Size: 2036 bytes --]
On Mon, 06 Oct 2003 19:56:05 +0200
Jan Schubert <Jan.Schubert@GMX.li> wrote:
> >-g (who's been too lazy to attempt the atkbd.c patchery needed to fix
> >this)
> >
> So, i assume you will fix this?
Wrong. I know basically nothing about the input/keyboard code. But...
Andries Brouwer posted, in another thread, that one should be able to
take the code from the message, and edit the table atkbd_set2_keycode...
Were it that simple (my patch is attached). For the two buttons that
yielded the error message, I changed the 0 to the keycode that 2.4 used
to provide...
So this makes the messages go away, that's only half the battle. If you
run with this patch, you'll notice that the Prev button generates the
same X keycode as the End key (which is busted).
I have no earthly idea how the keycodes in atkdb.c map to X keycodes.
Maybe somebody can explain it in a simple way...
-g
===== /ws/georgn/bk/keller-kernels/keller-2.6/drivers/input/keyboard/atkbd.c 1.37 vs edited =====
--- 1.37/drivers/input/keyboard/atkbd.c Fri Sep 26 02:56:26 2003
+++ edited//ws/georgn/bk/keller-kernels/keller-2.6/drivers/input/keyboard/atkbd.c Mon Oct 6 14:30:39 2003
@@ -65,13 +65,13 @@
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,255,
0, 0, 92, 90, 85, 0,137, 0, 0, 0, 0, 91, 89,144,115, 0,
- 217,100,255, 0, 97,165,164, 0,156, 0, 0,140,115, 0, 0,125,
+ 217,100,255, 0, 97,165,164, 0,156, 0, 0,140,115, 0, 131,125,
173,114, 0,113,152,163,151,126,128,166, 0,140, 0,147, 0,127,
159,167,115,160,164, 0, 0,116,158, 0,150,166, 0, 0, 0,142,
157, 0,114,166,168, 0, 0,213,155, 0, 98,113, 0,163, 0,138,
226, 0, 0, 0, 0, 0,153,140, 0,255, 96, 0, 0, 0,143, 0,
133, 0,116, 0,143, 0,174,133, 0,107, 0,105,102, 0, 0,112,
- 110,111,108,112,106,103, 0,119, 0,118,109, 0, 99,104,119
+ 110,111,108,112,106,103, 129,119, 0,118,109, 0, 99,104,119
};
static unsigned char atkbd_set3_keycode[512] = {
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-10-06 20:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-04 10:17 Jan Schubert
2003-10-06 2:37 ` Valdis.Kletnieks
2003-10-06 7:56 ` Jan Schubert
2003-10-06 10:34 ` Massimo Dal Zotto
2003-10-06 11:00 ` Jan Schubert
2003-10-06 17:42 ` Georg Nikodym
2003-10-06 17:56 ` Jan Schubert
2003-10-06 20:00 ` Georg Nikodym [this message]
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=20031006160049.6e428690.georgn@somanetworks.com \
--to=georgn@somanetworks.com \
--cc=Jan.Schubert@GMX.li \
--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
all inboxes | Powered by JetHome®