From: Kevin Shanahan <kmshanah@ucwb.org.au>
To: linux-kernel@vger.kernel.org
Subject: Re: Problems with input on 2.6
Date: Tue, 03 Feb 2004 17:00:29 +1030 [thread overview]
Message-ID: <1075789828.9311.2.camel@localhost> (raw)
In-Reply-To: <20040203055321.GB25849@ss1000.ms.mff.cuni.cz>
On Tue, 2004-02-03 at 16:23, Rudo Thomas wrote:
> Some of the questions you ask are answered in the Input FAQ that was posted
> just few days ago. Search the archives.
Sorry, I can't believe I missed that. Yes, I removed the 2nd pointer
definition from XF86Config-4 and this has fixed the double clicking and
movement precision issues.
Sorry for the noise.
Regards,
Kevin.
prev parent reply other threads:[~2004-02-03 6:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-03 5:34 Problems with input on 2.6 Kevin Shanahan
2004-02-03 5:53 ` Rudo Thomas
2004-02-03 6:30 ` Kevin Shanahan [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=1075789828.9311.2.camel@localhost \
--to=kmshanah@ucwb.org.au \
--cc=linux-kernel@vger.kernel.org \
/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