From: "Joseph Fannin" <jhf@rivenstone.net>
To: Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Synaptics TouchPad driver for 2.5.70
Date: Wed, 11 Jun 2003 11:30:30 -0400 [thread overview]
Message-ID: <20030611153030.GA4787@rivenstone.net> (raw)
In-Reply-To: <m2u1axk0kp.fsf@p4.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1187 bytes --]
On Wed, Jun 11, 2003 at 12:52:06AM +0200, Joseph Fannin wrote:
Please note that I did not write this driver -- Peter Osterlund
<petero2@telia.com> did. I meant only to forward this here, since the
original sender seems to have problems getting through to the list.
> Hi!
>
> Here is a driver for the Synaptics TouchPad for 2.5.70. It is largely
> based on the XFree86 driver. This driver operates the touchpad in
> absolute mode and emulates a three button mouse with two scroll
> wheels. Features include:
>
> * Multi finger tapping.
> * Vertical and horizontal scrolling.
> * Edge scrolling during drag operations.
> * Palm detection.
> * Corner tapping.
>
> The only major missing feature is runtime configuration of driver
> parameters. What is the best way to implement that? I was thinking of
> sending EV_MSC events to the driver using the /dev/input/event*
> interface and define my own codes for the different driver parameters.
>
> Comments?
--
Joseph Fannin
jhf@rivenstone.net
Rothchild's Rule -- "For every phenomenon, however complex, someone will
eventually come up with a simple and elegant theory. This theory will
be wrong."
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-06-11 15:16 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-10 22:52 [PATCH] Synaptics TouchPad driver for 2.5.70 Joseph Fannin
2003-06-11 15:30 ` Joseph Fannin [this message]
2003-06-11 20:17 ` Andrew Morton
2003-06-11 20:29 ` Vojtech Pavlik
2003-06-11 22:12 ` Peter Osterlund
[not found] <m2smqhqk4k.fsf@p4.localdomain>
2003-06-11 15:02 ` Vojtech Pavlik
2003-06-11 18:16 ` Peter Osterlund
2003-06-11 18:26 ` Vojtech Pavlik
2003-06-11 18:29 ` AlberT
2003-06-11 18:34 ` Vojtech Pavlik
2003-06-11 21:23 ` Peter Osterlund
2003-06-12 2:48 ` Joseph Fannin
2003-06-12 2:54 ` CaT
2003-06-12 18:58 ` Peter Osterlund
2003-06-12 22:01 ` Peter Berg Larsen
2003-06-12 22:57 ` Vojtech Pavlik
2003-06-12 23:17 ` Peter Berg Larsen
2003-06-12 23:27 ` Vojtech Pavlik
2003-06-12 23:42 ` Peter Berg Larsen
2003-06-13 7:44 ` Vojtech Pavlik
2003-06-13 8:58 ` Peter Berg Larsen
2003-06-13 20:25 ` James Simmons
2003-06-13 20:38 ` Vojtech Pavlik
2003-06-13 20:51 ` James Simmons
2003-06-13 22:08 ` Vojtech Pavlik
2003-06-13 23:57 ` James Simmons
2003-06-14 8:55 ` Vojtech Pavlik
2003-06-16 21:28 ` James Simmons
2003-06-12 19:11 ` Peter Osterlund
2003-06-12 6:31 ` Vojtech Pavlik
2003-06-12 8:36 ` James H. Cloos Jr.
2003-06-13 21:15 ` Peter Osterlund
2003-06-13 21:49 ` James Simmons
2003-06-13 22:08 ` Vojtech Pavlik
2003-06-13 22:55 ` Peter Berg Larsen
2003-06-14 8:42 ` Vojtech Pavlik
2003-06-14 22:19 ` Vojtech Pavlik
2003-06-15 12:18 ` Peter Osterlund
2003-06-15 12:28 ` Vojtech Pavlik
2003-06-15 15:47 ` Peter Osterlund
2003-06-15 17:27 ` Vojtech Pavlik
2003-06-18 23:41 ` Peter Osterlund
2003-06-19 6:03 ` Vojtech Pavlik
2003-06-23 16:30 ` Andreas Jellinghaus
2003-06-23 19:04 ` Peter Osterlund
2003-06-26 20:01 ` Vojtech Pavlik
2003-07-07 23:06 ` Peter Osterlund
2003-07-12 10:51 ` Andreas Jellinghaus
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=20030611153030.GA4787@rivenstone.net \
--to=jhf@rivenstone.net \
--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 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.