public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Tobias Ringstrom <tori@ringstrom.mine.nu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.40: AT keyboard input problem
Date: Mon, 7 Oct 2002 14:31:33 +0200	[thread overview]
Message-ID: <20021007143133.A477@ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.44.0210031442500.14559-100000@boris.prodako.se>; from tori@ringstrom.mine.nu on Thu, Oct 03, 2002 at 02:43:04PM +0200

On Thu, Oct 03, 2002 at 02:43:04PM +0200, Tobias Ringstrom wrote:
> On Thu, 3 Oct 2002, Vojtech Pavlik wrote:
> 
> > Good. You can use that for now, and I'll make a fix so that it works
> > even without it.
> 
> Great, thanks!

Ok, here is the promised fix. I'll send it to Linus soon.

===================================================================

diff -Nru a/drivers/input/serio/i8042.c b/drivers/input/serio/i8042.c
--- a/drivers/input/serio/i8042.c	Mon Oct  7 14:30:14 2002
+++ b/drivers/input/serio/i8042.c	Mon Oct  7 14:30:14 2002
@@ -63,7 +63,7 @@
 
 extern struct pt_regs *kbd_pt_regs;
 
-static unsigned long i8042_unxlate_seen[128 / BITS_PER_LONG];
+static unsigned long i8042_unxlate_seen[256 / BITS_PER_LONG];
 static unsigned char i8042_unxlate_table[128] = {
 	  0,118, 22, 30, 38, 37, 46, 54, 61, 62, 70, 69, 78, 85,102, 13,
 	 21, 29, 36, 45, 44, 53, 60, 67, 68, 77, 84, 91, 90, 20, 28, 27,
@@ -407,14 +407,14 @@
 		}
 
 		if (data > 0x7f) {
-			if (test_and_clear_bit(data & 0x7f, i8042_unxlate_seen)) {
+			if (test_and_clear_bit((data & 0x7f) | (i8042_last_e0 << 7), i8042_unxlate_seen)) {
 				serio_interrupt(&i8042_kbd_port, 0xf0, dfl);
 				if (i8042_last_e0 && (data == 0xaa || data == 0xb6))
-					set_bit(data & 0x7f, i8042_unxlate_seen);
+					set_bit((data & 0x7f) | (i8042_last_e0 << 7), i8042_unxlate_seen);
 				data = i8042_unxlate_table[data & 0x7f];
 			}
 		} else {
-			set_bit(data, i8042_unxlate_seen);
+			set_bit(data | (i8042_last_e0 << 7), i8042_unxlate_seen);
 			data = i8042_unxlate_table[data];
 		}
 

===================================================================

-- 
Vojtech Pavlik
SuSE Labs

  parent reply	other threads:[~2002-10-07 12:26 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-03  6:59 2.5.40: AT keyboard input problem Tobias Ringstrom
2002-10-03  7:15 ` DevilKin
2002-10-03  8:36 ` jbradford
2002-10-03  8:48   ` Vojtech Pavlik
2002-10-03 10:14     ` jbradford
2002-10-03 10:13       ` Vojtech Pavlik
2002-10-03 11:34         ` jbradford
2002-10-03 11:31           ` Vojtech Pavlik
2002-10-03 12:42             ` jbradford
2002-10-03 12:43               ` Vojtech Pavlik
2002-10-03 13:20                 ` jbradford
2002-10-03 13:17                   ` Vojtech Pavlik
2002-10-03 13:40                   ` Vojtech Pavlik
2002-10-03 13:44                   ` Bruce Harada
2002-10-03 17:43                   ` Andries Brouwer
2002-10-03  8:47 ` Vojtech Pavlik
2002-10-03 12:08   ` Tobias Ringstrom
2002-10-03 12:10     ` Vojtech Pavlik
2002-10-03 12:28       ` Tobias Ringstrom
2002-10-03 12:31         ` Vojtech Pavlik
     [not found]           ` <Pine.LNX.4.44.0210031442500.14559-100000@boris.prodako.se>
2002-10-07 12:31             ` Vojtech Pavlik [this message]
2002-10-03 12:48 ` Jon Portnoy
2002-10-03 12:51   ` Vojtech Pavlik

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=20021007143133.A477@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tori@ringstrom.mine.nu \
    /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