public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Kris Karas <ktk@enterprise.bidmc.harvard.edu>
Cc: Pavel Machek <pavel@ucw.cz>,
	linux-kernel@vger.kernel.org, Greg Stark <gsstark@mit.edu>
Subject: Re: Problem report: 2.6.12-rc4 ps2 keyboard being misdetected as /dev/input/mouse0
Date: Mon, 23 May 2005 00:27:36 -0500	[thread overview]
Message-ID: <200505230027.37308.dtor_core@ameritech.net> (raw)
In-Reply-To: <428BBEED.6090608@enterprise.bidmc.harvard.edu>

On Wednesday 18 May 2005 17:17, Kris Karas wrote:
> Dmitry Torokhov wrote:
> 
> >On 5/18/05, Pavel Machek <pavel@ucw.cz> wrote:
> >  
> >
> >>>Although... maybe the patch below is not too ugly.
> >>>      
> >>>
> >>Looks pretty much okay to me...
> >>    
> >>
> >
> >Does it work for you? If so I'll send it to Andrew to simmer in -mm.
> >  
> >
> 
> FWIW, I've tested the patch and it seems to be working just fine.  Thanks!
> 
> There is one exception, though it does not appear to be related to the 
> mouse code or the patch, as far as I can tell.   Pressing or releasing 
> the right-windows key sends a blank event to GPM (as reported by 'mev') 
> causing the mouse cursor to reappear.  If I use "showkey -s" to tell me 
> the scancode, nothing happens.  The key is evidently bound in the kernel 
> table, else I'd see the obligatory PRINTK encouraging me to bind it.  So 
> something is intercepting the key and sending it to GPM.   
> Experimentally, it appears as if the key press is delivered only if it 
> has not been pressed for roughly 3 seconds (256 Jiffies???).
> 

I wonder if the this patch from Vojtech will cure that problem...

-- 
Dmitry

===================================================================
From: Vojtech Pavlik <vojtech@suse.cz>

Input: Fix fast scrolling scancodes in atkbd.c

Signed-off-by: Vojtech Pavlik <vojtech@suse.cz>
--

 atkbd.c |    6 +++---
 1 files changed, 3 insertions(+), 3 deletions(-)

Index: dtor/drivers/input/keyboard/atkbd.c
===================================================================
--- dtor.orig/drivers/input/keyboard/atkbd.c
+++ dtor/drivers/input/keyboard/atkbd.c
@@ -171,9 +171,9 @@ static struct {
 	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 },


  reply	other threads:[~2005-05-23  5:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-16  5:12 Problem report: 2.6.12-rc4 ps2 keyboard being misdetected as /dev/input/mouse0 Greg Stark
2005-05-16  5:36 ` Dmitry Torokhov
2005-05-17  3:42   ` Kris Karas
2005-05-17  4:58     ` Dmitry Torokhov
2005-05-18 11:13       ` Pavel Machek
2005-05-18 13:39         ` Dmitry Torokhov
2005-05-18 22:17           ` Kris Karas
2005-05-23  5:27             ` Dmitry Torokhov [this message]
2005-05-18 11:12   ` Pavel Machek

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=200505230027.37308.dtor_core@ameritech.net \
    --to=dtor_core@ameritech.net \
    --cc=gsstark@mit.edu \
    --cc=ktk@enterprise.bidmc.harvard.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.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