From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, gunther.mayer@gmx.net
Subject: Re: PS2 Input Core Support
Date: Thu, 18 Jul 2002 12:17:51 +0200 [thread overview]
Message-ID: <B3D59960FB3@vcnet.vc.cvut.cz> (raw)
On 17 Jul 02 at 16:01, Vojtech Pavlik wrote:
> On Wed, Jul 17, 2002 at 03:58:21PM +0200, Gunther Mayer wrote:
>
> > > > 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
> > }
>
> Cool! Anyone send me a patch? ;)
Been there, done that... and unfortunately, my WOP35 insist on
taking first 6 bytes as PS/2->ImPS/2 sequence, and rest as normal
DPI settings. I tried it in reverse order, and couple of permutations,
but it still returns ExPS/2 id. I tried also other sequences from
gm_psauxprint-0.01, but I found nothing interesting, except that
mouse definitely does not support MS PNP id.
Answer from A4Tech support was that mouse is not supported under Linux,
and that I should use Windows and verify that mouse is properly connected.
So I'm on the best way to the command line switch, I think. Google
find couple of problem reporters, but nobody found detection method :-(
Petr Vandrovec
vandrove@vc.cvut.cz
next reply other threads:[~2002-07-18 10:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-18 10:17 Petr Vandrovec [this message]
2002-07-18 12:58 ` PS2 Input Core Support 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-17 13:24 Petr Vandrovec
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 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=B3D59960FB3@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=gunther.mayer@gmx.net \
--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