public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: Kris Karas <ktk@enterprise.bidmc.harvard.edu>,
	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: Wed, 18 May 2005 13:13:22 +0200	[thread overview]
Message-ID: <20050518111322.GC1952@elf.ucw.cz> (raw)
In-Reply-To: <200505162358.15099.dtor_core@ameritech.net>

Hi!

> > >>I just updated to 2.6.12-rc4 and now /dev/input/mouse0 seems to be my ps2
> > >>keyboard.
> > >>
> > >Please use /dev/input/mice for accessing your mouse.
> > >
> > 
> > One possibly interesting mouse issue in 2.6.12-rc[1..4] is that when 
> > using /dev/psaux, I have found that my mouse cursor under GPM seems to 
> > be triggered into un-hiding when I issue some random number of 
> > non-hiding key-down events.  That is, press and release the keyboard 
> > shift key say 3 or 5 or 10 times, and the console mouse cursor will 
> > appear, just as if the mouse had been moved.  This bug is not in 2.6.11 
> > (nor Alan's 2.6.11-ac7, fwiw).
> > 
> 
> This is caused by atkbd's scrolling support + GPM not expecting to see a
> 0-motion packets from devices... I'd say we need to fix GPM not to set
> GPM_MOVE in these cases; I have looked into adjusting mousedev but it is
> too ugly for words to suppress them there.
> 
> Although... maybe the patch below is not too ugly.

Looks pretty much okay to me...
								Pavel

  reply	other threads:[~2005-05-18 11:18 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 [this message]
2005-05-18 13:39         ` Dmitry Torokhov
2005-05-18 22:17           ` Kris Karas
2005-05-23  5:27             ` Dmitry Torokhov
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=20050518111322.GC1952@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=dtor_core@ameritech.net \
    --cc=gsstark@mit.edu \
    --cc=ktk@enterprise.bidmc.harvard.edu \
    --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