From: Christoph Hellwig <hch@infradead.org>
To: Stuffed Crust <pizza@shaftnet.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [2.5.68] [BUG #18] Add Synaptics touchpad tweaking to psmouse driver
Date: Wed, 23 Apr 2003 18:13:39 +0100 [thread overview]
Message-ID: <20030423181339.A2904@infradead.org> (raw)
In-Reply-To: <20030422024628.GA8906@shaftnet.org>; from pizza@shaftnet.org on Mon, Apr 21, 2003 at 10:46:28PM -0400
On Mon, Apr 21, 2003 at 10:46:28PM -0400, Stuffed Crust wrote:
> One of the side-effects of the new input layer is that the old usermode
> tools for manipulating the touchpad configuration don't work any more.
>
> Most importantly, the ability to disable the tap-to-click "feature".
> And this has been long-recognized, as bug #18. :)
>
> So, here's my crack at scratching this itch. it defaults to disabling
> the tap-to-click, but there's a module parameter to re-enable it.
>
> I started writing this from the perspective of a full-native synaptics
> driver, using the absolute mode of operation, which will let us do all
> sorts of yummy things like corner taps and virtual scroll wheels and
> sensitivity and whatnot... Anyone else working on this, before I wade
> further in?
>
> All of the new code is wrapped in #ifdef SYNAPTICS.
This is messy as hell - what about copying psmouse.c, remove all
that code not relevant to the touchpad and make it a driver of it's
own?
next prev parent reply other threads:[~2003-04-23 17:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-22 2:46 [PATCH] [2.5.68] [BUG #18] Add Synaptics touchpad tweaking to psmouse driver Stuffed Crust
2003-04-23 17:03 ` CaT
2003-04-23 17:10 ` Stuffed Crust
2003-04-23 17:13 ` Christoph Hellwig [this message]
2003-04-23 17:37 ` Stuffed Crust
2003-04-25 0:58 Perez-Gonzalez, Inaky
2003-04-25 1:34 ` Stuffed Crust
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=20030423181339.A2904@infradead.org \
--to=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pizza@shaftnet.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;
as well as URLs for NNTP newsgroup(s).