From: Kim Holviala <kim@holviala.com>
To: Kim Holviala <kim@holviala.com>
Cc: Vojtech Pavlik <vojtech@suse.cz>,
Dmitry Torokhov <dtor_core@ameritech.net>,
linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] mousedev: Fix scrollwheel thingy on IBM ScrollPoint mice
Date: Thu, 28 Oct 2004 15:42:43 +0300 [thread overview]
Message-ID: <4180E943.8060203@holviala.com> (raw)
In-Reply-To: <417F411A.4090401@holviala.com>
Kim Holviala wrote:
>>>>> 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 */
>>>>
>>
>> We can have a workaround for XOrg, but not one like this. This will make
>> fast scrolling unreliable. I have standard Microsoft-compatible mice
>> which do report more than one scroll tick per report, if you scroll the
>> wheel fast enough, and this throws away the extra ticks.
One more comment to the scrollpoint issue: if they haven't fixed it
after 4.3.something XFree throws away all scroll events where the scroll
amount is more than 1. So "fast scrolling" is already unreliable, this
patch just made it work somehow instead of what it's doing now: not
working at all.
Kim
prev parent reply other threads:[~2004-10-28 12:42 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
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 [this message]
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=4180E943.8060203@holviala.com \
--to=kim@holviala.com \
--cc=akpm@osdl.org \
--cc=dtor_core@ameritech.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 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.