From: Kieran <kieran@ihateaol.co.uk>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: uk keyboard broken by input updates?
Date: Mon, 12 Jan 2004 19:36:18 +0000 [thread overview]
Message-ID: <4002F732.6020609@ihateaol.co.uk> (raw)
In-Reply-To: <20040112103256.GA4038@ucw.cz>
> On Mon, Jan 12, 2004 at 10:21:04AM +0000, Kieran wrote:
>
>>I have exactly the same problem using 2.6.1 and an IBM USB keyboard, not
>>really had a chance to look into it yet though.
>
>
> Can you check if this fixes it for you?
>
> diff -Nru a/drivers/char/keyboard.c b/drivers/char/keyboard.c
> --- a/drivers/char/keyboard.c Sun Jan 11 19:42:55 2004
> +++ b/drivers/char/keyboard.c Sun Jan 11 19:42:55 2004
> @@ -941,8 +941,8 @@
> 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47,
> 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63,
> 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79,
> - 80, 81, 82, 83, 84, 93, 86, 87, 88, 94, 95, 85,259,375,260, 90,
> - 284,285,309,311,312, 91,327,328,329,331,333,335,336,337,338,339,
> + 80, 81, 82, 83, 43, 93, 86, 87, 88, 94, 95, 85,259,375,260, 90,
> + 284,285,309,298,312, 91,327,328,329,331,333,335,336,337,338,339,
> 367,288,302,304,350, 89,334,326,116,377,109,111,126,347,348,349,
> 360,261,262,263,298,376,100,101,321,316,373,286,289,102,351,355,
> 103,104,105,275,287,279,306,106,274,107,294,364,358,363,362,361,
>
works perfectly
##~~
:-)
next prev parent reply other threads:[~2004-01-12 19:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-12 10:03 uk keyboard broken by input updates? Bastien Nocera
2004-01-12 10:21 ` Kieran
2004-01-12 10:32 ` Vojtech Pavlik
2004-01-12 19:36 ` Kieran [this message]
2004-01-12 21:15 ` Bastien Nocera
2004-01-23 8:58 ` Bastien Nocera
2004-01-23 9:29 ` Andrew Morton
2004-01-23 9:37 ` Bastien Nocera
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=4002F732.6020609@ihateaol.co.uk \
--to=kieran@ihateaol.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox