public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Zephaniah E\. Hull" <warp@babylon.d2dc.net>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [patch] Problem with mousedev.c
Date: Wed, 30 Oct 2002 10:32:57 -0500	[thread overview]
Message-ID: <20021030153257.GA27585@babylon.d2dc.net> (raw)
In-Reply-To: <20021028184008.B32183@ucw.cz>

[-- Attachment #1: Type: text/plain, Size: 2529 bytes --]

On Mon, Oct 28, 2002 at 06:40:08PM +0100, Vojtech Pavlik wrote:
> On Sat, Oct 26, 2002 at 09:05:38PM -0400, Zephaniah E. Hull wrote:
> > To make a long story short, mousedev.c does not properly implement the
> > EXPS/2 protocol, specificly dealing with the wheel.
> > 
> > The lower 8 bits of the 4th byte are supposed to be 0x1 or 0xf to
> > indicate movement of the first wheel, and 0x2 or 0xe for the second
> > wheel.
> 
> No, see microsoft documentation. They're expected to be a 4-bit signed
> binary complement value that indicates the amount of movement.

After some poking, two questions.

The first is the URL for the documentation in question? This seems
inconsistent with what I remember reading in the past, but can't seem to
find anymore.

The second is if you have actually seen hardware which /actually/
generates the wheel data described while speaking exps2?
> 
> > Attached is a patch to correct this.
> > 
> > This does not get my two wheel mouse working perfectly yet, sadly that
> > will take a bit of a hack, and I'm not sure where the best place to put
> > it is yet, but this gets it back to generating correct data.
> 
> PS/2 A4-Tech mouse do the ugly trick you describe above to stuff two
> wheel information into a single-wheel oriented ImExPS/2 protocol. USB
> A4-Tech mouse do another ugly trick (additional button which specifies
> which wheel is rotating). I'm not interested in supporting these ugly
> tricks.

Sadly, if PS/2 mice are any indication, mouse makers /will/ manage to
fuck things up on enough popular mice under USB as well, and there needs
to be a place to shove the dirty hacks needed to make things Just Work
for users..

At least with USB stuff we can /identify/ the damn things, which means
that we are leaps and bounds ahead of where we are for PS2 stuff.
> 
> If you want to support the H-Wheel in GPM, then please add
> /dev/input/event support into GPM. (simple patch attached, you may need
> to do more changes, namely for h-wheel).

Thanks, my next gpm upload should include it, now to get support for the
same for X.. (Arrgh, X hacking is even lower on my list of things to do
then kernel hacking is. Probably because I've done more of it.)

-- 
	1024D/E65A7801 Zephaniah E. Hull <warp@babylon.d2dc.net>
	   92ED 94E4 B1E6 3624 226D  5727 4453 008B E65A 7801
	    CCs of replies from mailing lists are requested.

Has anyone got a reference cynic? I think I need to recalibrate myself.
  -- James Riden in the SDM.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2002-10-30 15:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-27  1:05 [patch] Problem with mousedev.c Zephaniah E. Hull
2002-10-28 13:27 ` Petr Vandrovec
2002-10-28 17:00   ` Zephaniah E. Hull
2002-10-28 17:40 ` Vojtech Pavlik
2002-10-30 15:32   ` Zephaniah E. Hull [this message]
2002-10-30 15:59     ` Vojtech Pavlik
2002-10-30 16:04       ` Zephaniah E. Hull
2002-10-30 16:11         ` Vojtech Pavlik
2002-10-30 16:21           ` Zephaniah E. Hull
  -- strict thread matches above, loose matches on Subject: below --
2002-10-30 16:46 Petr Vandrovec
2002-10-30 18:37 ` Zephaniah E. Hull

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=20021030153257.GA27585@babylon.d2dc.net \
    --to=warp@babylon.d2dc.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