From: Wakko Warner <wakko@animx.eu.org>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.12-rc2: Compose key doesn't work
Date: Mon, 30 May 2005 10:25:15 -0400 [thread overview]
Message-ID: <20050530142515.GA20372@animx.eu.org> (raw)
In-Reply-To: <20050526155344.GB3694@ucw.cz>
Vojtech Pavlik wrote:
> On Thu, May 26, 2005 at 11:45:09AM -0400, Wakko Warner wrote:
> > I do wish they'd fix it, because I use this key (kinda like another ALT key)
> > more than my compose key (again, the menu key, not the right win logo key)
>
> This patch should fix it.
At work, I have a USB keyboard with 8 extra keys. Could something like this
be the cause of about 5 of those keys not working? (They worked under 2.4
perfectly)
> atkbd.c | 6 +++---
> 1 files changed, 3 insertions(+), 3 deletions(-)
>
>
> diff -Nru a/drivers/input/keyboard/atkbd.c b/drivers/input/keyboard/atkbd.c
> --- a/drivers/input/keyboard/atkbd.c 2005-05-03 15:23:34 +02:00
> +++ b/drivers/input/keyboard/atkbd.c 2005-05-03 15:23:34 +02:00
> @@ -171,9 +171,9 @@
> unsigned char set2;
> } atkbd_scroll_keys[] = {
> { ATKBD_SCR_1, 0xc5 },
> - { ATKBD_SCR_2, 0xa9 },
> - { ATKBD_SCR_4, 0xb6 },
> - { ATKBD_SCR_8, 0xa7 },
> + { ATKBD_SCR_2, 0x9d },
> + { ATKBD_SCR_4, 0xa4 },
> + { ATKBD_SCR_8, 0x9b },
> { ATKBD_SCR_CLICK, 0xe0 },
> { ATKBD_SCR_LEFT, 0xcb },
> { ATKBD_SCR_RIGHT, 0xd2 },
--
Lab tests show that use of micro$oft causes cancer in lab animals
next prev parent reply other threads:[~2005-05-30 14:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-10 9:52 2.6.12-rc2: Compose key doesn't work Rene Herman
2005-04-14 10:04 ` Domen Puncer
2005-05-26 12:23 ` Domen Puncer
2005-05-26 12:27 ` Vojtech Pavlik
2005-06-03 21:16 ` Wakko Warner
2005-06-03 21:37 ` Dmitry Torokhov
2005-05-26 15:45 ` Wakko Warner
2005-05-26 15:53 ` Vojtech Pavlik
2005-05-26 16:09 ` Wakko Warner
2005-05-30 14:25 ` Wakko Warner [this message]
2005-05-30 14:39 ` Vojtech Pavlik
2005-05-30 23:03 ` Rene Herman
2005-04-14 11:18 ` Kees Bakker
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=20050530142515.GA20372@animx.eu.org \
--to=wakko@animx.eu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.cz \
/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.