From: Mark Lord <lkml@rtr.ca>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
rubini@vision.unipv.it, linux-input@vger.kernel.org,
Linux Kernel <linux-kernel@vger.kernel.org>,
Jeff Garzik <jeff@garzik.org>
Subject: Re: 2.6.24: false double-clicks from USB mouse
Date: Sun, 02 Dec 2007 13:17:43 -0500 [thread overview]
Message-ID: <4752F6C7.4040904@rtr.ca> (raw)
In-Reply-To: <Pine.LNX.4.64.0712021903460.12208@twin.jikos.cz>
Jiri Kosina wrote:
> On Sun, 2 Dec 2007, Mark Lord wrote:
>
>>> Single-clicking on things with 2.6.24 very frequently gives a
>>> "double-click". This does not happen with 2.6.23.8. I wonder what
>>> broke it? I've grabbed mousedev.c from 2.6.23 and inserted that in
>>> place of the updated 2.6.24 source, but no change. So it's not that
>>> file.
>> Mmm.. reverting the entire drivers/hid directory to that from 2.6.23
>> seems to have fixed the problem, so we now know it's in there somewhere.
...
Mmmm.. an update here:
Reverting the drivers/hid directory does seem to improve behaviour.
But right now I have a "make -j4" happening in the background
and the mouse is ever so erratic again, despite the drivers/hid reversion.
So it's a timing thing, somewhere.
Maybe a scheduling thing?
Jiri: I know nothing about how mouse clicks are interpreted,
or even *where* or *how* double-click detection happens.
Until this started happening, I didn't even know which module
was the driver for my mouse (it's usbhid).
Can you give a short tutorial, to help us understand possible causes ?
next prev parent reply other threads:[~2007-12-02 18:17 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-02 16:21 2.6.24: false double-clicks from USB mouse Mark Lord
2007-12-02 16:58 ` Mark Lord
2007-12-02 17:04 ` REGRESSION: " Mark Lord
2007-12-02 17:07 ` Arjan van de Ven
2007-12-02 17:14 ` Mark Lord
2007-12-02 17:57 ` Jeff Garzik
2007-12-02 18:09 ` Jiri Kosina
2007-12-06 8:27 ` Diego Zuccato
2007-12-06 12:21 ` Jiri Kosina
2007-12-02 18:07 ` Jiri Kosina
2007-12-02 18:17 ` Mark Lord [this message]
2007-12-02 18:20 ` Mark Lord
2007-12-02 18:23 ` Jiri Kosina
2007-12-02 18:48 ` Mark Lord
2007-12-02 18:52 ` Mark Lord
2007-12-02 19:09 ` Jiri Kosina
2007-12-02 19:24 ` Mark Lord
2007-12-02 19:27 ` Jiri Kosina
2007-12-02 19:44 ` Mark Lord
2007-12-02 22:07 ` Jiri Kosina
2007-12-02 22:46 ` Mark Lord
2007-12-07 17:59 ` Ray Lee
2007-12-07 18:32 ` Dmitry Torokhov
2007-12-07 21:23 ` Ray Lee
2007-12-07 21:43 ` Dmitry Torokhov
2007-12-02 18:06 ` Oliver Neukum
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=4752F6C7.4040904@rtr.ca \
--to=lkml@rtr.ca \
--cc=dmitry.torokhov@gmail.com \
--cc=jeff@garzik.org \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rubini@vision.unipv.it \
/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;
as well as URLs for NNTP newsgroup(s).