From: Gunther Mayer <gunther.mayer@gmx.net>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Petr Vandrovec <VANDROVE@vc.cvut.cz>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: PS2 Input Core Support
Date: Wed, 17 Jul 2002 15:58:21 +0200 [thread overview]
Message-ID: <3D3577FD.ED42443C@gmx.net> (raw)
In-Reply-To: 20020717150153.B19609@ucw.cz
Vojtech Pavlik wrote:
> 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 ... ?
from http://home.t-online.de/home/gunther.mayer/gm_psauxprint-0.01.c :
char a4tech_id[]={ 0xf3,200, 0xf3,100, 0xf3,80, 0xf3,60, 0xf3,40, 0xf3,20};
if(a4tech) {
sendbuf(fd,f,a4tech_id,12);
buf[0]=0xf2;
write(fd,&buf,1);
b=consumefa(f);
printf("a4tech ID(f2) is %x\n",b);
if(b==6 || b==8) printf("AUTODETECT: a4tech\n");
// b=6: spiffy gyro-mouse "8D Profi-Mouse Point Stick"
// b=8: boeder Smartmouse Pro (4Button, 2Scrollwheel, 520dpi) PSM_4DPLUS_ID MOUSE_MODEL_4DPLUS
}
next prev parent reply other threads:[~2002-07-17 13:54 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
2002-07-17 13:58 ` Gunther Mayer [this message]
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=3D3577FD.ED42443C@gmx.net \
--to=gunther.mayer@gmx.net \
--cc=VANDROVE@vc.cvut.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.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