public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: "Udo A. Steinberg" <reality@delusion.de>
Cc: Vojtech Pavlik <vojtech@suse.cz>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: PS2 Input Core Support
Date: Wed, 17 Jul 2002 12:20:00 +0200	[thread overview]
Message-ID: <20020717122000.A12529@ucw.cz> (raw)
In-Reply-To: <3D35435F.E5CFA5E2@delusion.de>; from reality@delusion.de on Wed, Jul 17, 2002 at 12:13:51PM +0200

On Wed, Jul 17, 2002 at 12:13:51PM +0200, Udo A. Steinberg wrote:
> 
> Hi Vojtech,
> 
> I'm running 2.5.26 with an ordinary PS/2 keyboard and a 5 button PS/2 mouse.
> When using the old psaux driver the mouse works fine.
> With input core support, however, the scroll wheel doesn't work properly.
> In my XF86Config I'm using IMPS/2 protocol and ZAxisMapping 4 5.
> Scrolling up causes the window to scroll down. Scrolling down doesn't do
> anything. When changing the protocol to ExplorerPS2 things are not much
> better. You can't drag windows over the screen.
> 
> The following is the relevant kernel information.
> Do you have any tips?

It's a bug. This patch should fix it:

diff -Nru a/drivers/input/mouse/psmouse.c b/drivers/input/mouse/psmouse.c
--- a/drivers/input/mouse/psmouse.c	Wed Jul 17 12:19:13 2002
+++ b/drivers/input/mouse/psmouse.c	Wed Jul 17 12:19:13 2002
@@ -142,7 +142,7 @@
  */
 
 	if (psmouse->type == PSMOUSE_IMEX) {
-		input_report_rel(dev, REL_WHEEL, (int) (packet[3] & 7) - (int) (packet[2] & 8));
+		input_report_rel(dev, REL_WHEEL, (int) (packet[2] & 8) - (int) (packet[3] & 7));
 		input_report_key(dev, BTN_SIDE, (packet[3] >> 4) & 1);
 		input_report_key(dev, BTN_EXTRA, (packet[3] >> 5) & 1);
 	}


> mice: PS/2 mouse device common for all mice
> input.c: calling /sbin/hotplug input [HOME=/ PATH=/sbin:/bin:/usr/sbin:/usr/bin ACTION=add PRODUC
> input.c: hotplug returned -2
> input: AT Set 2 keyboard on isa0060/serio0
> serio: i8042 KBD port at 0x60,0x64 irq 1  
> serio: i8042 AUX port at 0x60,0x64 irq 12
> input.c: calling /sbin/hotplug input [HOME=/ PATH=/sbin:/bin:/usr/sbin:/usr/bin ACTION=add PRODUC
> input.c: hotplug returned -2
> input: ImExPS/2 Microsoft IntelliMouse Explorer on isa0060/serio1
> 
> Regards,
> Udo.

-- 
Vojtech Pavlik
SuSE Labs

  reply	other threads:[~2002-07-17 10:17 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-17 10:13 PS2 Input Core Support Udo A. Steinberg
2002-07-17 10:20 ` Vojtech Pavlik [this message]
2002-07-17 11:47   ` Udo A. Steinberg
2002-07-17 12:10     ` Vojtech Pavlik
2002-07-17 12:15       ` Udo A. Steinberg
2002-07-17 12:29         ` Vojtech Pavlik
2002-07-17 12:41           ` Udo A. Steinberg
2002-07-17 12:44             ` Vojtech Pavlik
2002-07-17 12:54               ` Udo A. Steinberg
2002-07-17 13:00                 ` Vojtech Pavlik
2002-07-17 13:08                   ` Udo A. Steinberg
2002-07-17 10:23 ` Oliver Graf
  -- strict thread matches above, loose matches on Subject: below --
2002-07-17 12:55 Petr Vandrovec
2002-07-17 13:01 ` Vojtech Pavlik
2002-07-17 13:58   ` Gunther Mayer
2002-07-17 14:01     ` Vojtech Pavlik
2002-07-17 13:24 Petr Vandrovec
2002-07-18 10:17 Petr Vandrovec
2002-07-18 12:58 ` Vojtech Pavlik
2002-07-18 13:36 Petr Vandrovec
2002-07-18 13:45 ` 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=20020717122000.A12529@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reality@delusion.de \
    /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