public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Petr Vandrovec <VANDROVE@vc.cvut.cz>
Cc: Vojtech Pavlik <vojtech@suse.cz>,
	Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: PS2 Input Core Support
Date: Wed, 17 Jul 2002 15:01:53 +0200	[thread overview]
Message-ID: <20020717150153.B19609@ucw.cz> (raw)
In-Reply-To: <B27F96E7240@vcnet.vc.cvut.cz>; from VANDROVE@vc.cvut.cz on Wed, Jul 17, 2002 at 02:55:21PM +0200

On Wed, Jul 17, 2002 at 02:55:21PM +0200, Petr Vandrovec wrote:
> On 17 Jul 02 at 14:44, Vojtech Pavlik wrote:
> 
> > > --- 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] & 8) - (int) (packet[2] & 7));
> > > +               input_report_rel(dev, REL_WHEEL, (int) (packet[3] & 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);
> > >         }
> 
> Hi,
>   any plans to support A4Tech mouse? It uses IMEX protocol, but
>   
> switch(packet[3] & 0x0F) {
>     case 0: /* nothing */
>     case 1: vertical_wheel--; break;
>     case 2: horizontal_wheel++; break;
>     case 0xE: horizontal_wheel--; break;
>     case 0xF: vertical_wheel++; break;
> }
> 
> and obviously it never reports wheel move > 1 in one sample.

Is there a way to detect whether it's an ImEx or A4? Or will we need a
command line parameter ... ?

-- 
Vojtech Pavlik
SuSE Labs

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

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-17 12:55 PS2 Input Core Support Petr Vandrovec
2002-07-17 13:01 ` Vojtech Pavlik [this message]
2002-07-17 13:58   ` Gunther Mayer
2002-07-17 14:01     ` Vojtech Pavlik
  -- strict thread matches above, loose matches on Subject: below --
2002-07-18 13:36 Petr Vandrovec
2002-07-18 13:45 ` Vojtech Pavlik
2002-07-18 10:17 Petr Vandrovec
2002-07-18 12:58 ` Vojtech Pavlik
2002-07-17 13:24 Petr Vandrovec
2002-07-17 10:13 Udo A. Steinberg
2002-07-17 10:20 ` Vojtech Pavlik
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

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=20020717150153.B19609@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=VANDROVE@vc.cvut.cz \
    --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