All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor_core@ameritech.net>
To: linux-kernel@vger.kernel.org
Cc: Andrew Morton <akpm@osdl.org>, Kim Holviala <kim@holviala.com>,
	vojtech@suse.cz
Subject: Re: [PATCH] mousedev: Fix scrollwheel thingy on IBM ScrollPoint mice
Date: Tue, 26 Oct 2004 19:33:50 -0500	[thread overview]
Message-ID: <200410261933.50544.dtor_core@ameritech.net> (raw)
In-Reply-To: <20041026171157.21c7a15a.akpm@osdl.org>

On Tuesday 26 October 2004 07:11 pm, Andrew Morton wrote:
> Kim Holviala <kim@holviala.com> wrote:
> >
> > The scrollwheel thingy (stick) on IBM ScrollPoint mice returns extremely
> > aggressive values even when touched lightly. This confuses XFree which
> > assumes the wheel values can only be 1 or -1. Incidently, it also
> > confuses Windows' default mouse driver which proves the problem is in
> > the mouse itself.
> > 
> > This patch limits the scroll wheel movements to be either +1 or -1 on
> > the event -> emulated PS/2 level. I chose to implement it there because
> > mousedev emulates Microsoft mice but the real ones almoust never return
> > a bigger value than 1 (or -1).
> > ...
> > +#ifdef CONFIG_INPUT_MOUSEDEV_WHEELFIX
> > +				if (value) { value = (value < 0 ? -1 : 1); }
> > +#endif /* CONFIG_INPUT_MOUSEDEV_WHEELFIX */
> 
> This is really not a thing which we can put behind compile-time config.
> 
> Can we come up with a fix which works correctly on all hardware?  If not,
> this workaround will need to be enabled by some sort of runtime detection.
> 

Unless someone (Vojtech?) has an objection I think we should always have
this workaround activated - after all mousedev provides legacy emulation
mostly for XFree/XOrg benefit anyway. Clients accessing data through evdev
will see the full picture regardless.

-- 
Dmitry

  reply	other threads:[~2004-10-27  0:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-26  8:45 [PATCH] mousedev: Fix scrollwheel thingy on IBM ScrollPoint mice Kim Holviala
2004-10-27  0:11 ` Andrew Morton
2004-10-27  0:33   ` Dmitry Torokhov [this message]
2004-10-27  5:51     ` Vojtech Pavlik
2004-10-27  6:29       ` Dmitry Torokhov
2004-10-27  6:32       ` Kim Holviala
2004-10-28 12:42         ` Kim Holviala

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=200410261933.50544.dtor_core@ameritech.net \
    --to=dtor_core@ameritech.net \
    --cc=akpm@osdl.org \
    --cc=kim@holviala.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.