From: James Simmons <jsimmons@infradead.org>
To: Vojtech Pavlik <vojtech@ucw.cz>
Cc: Peter Berg Larsen <pebl@math.ku.dk>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Synaptics TouchPad driver for 2.5.70
Date: Sat, 14 Jun 2003 00:57:14 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.44.0306140045160.29353-100000@phoenix.infradead.org> (raw)
In-Reply-To: <20030614000857.B10851@ucw.cz>
> > > > Just as a idea for API. How about ABS_AREA or REL_AREA instead of
> > > > ABS_MISC. The idea is the pressure value returned should be about
> > > > the same if one presses hard with one finger or softly with a whole
> > > > hand.
> > >
> > > Huh? Force = Pressure x Area ... I think you're mixing up force and
> > > pressure here.
> >
> > OOps. Your right. I'm thinking the hardware returns a force value. What I
> > meant is since we have the hardware returning the pressure and the area
> > this data can be used. Knowing the area over which a pressure is applied
> > is a good thing. What do you think?
>
> Definitely. Still it doesn't cover the multi-tap/gesture stuff.
How about EV_AREA
codes = "which area" 1, 2, 3
value = "How big of a area"
struct input_event {
struct timeval time;
__u16 type; EV_AREA
__u16 code; AREA_1
__s32 value; 20
};
next prev parent reply other threads:[~2003-06-13 23:43 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m2smqhqk4k.fsf@p4.localdomain>
2003-06-11 15:02 ` [PATCH] Synaptics TouchPad driver for 2.5.70 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 [this message]
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-15 21:42 ` [PATCH] Synaptics Client/Passthrough (for Inspiron...) Arne Koewing
2003-06-13 21:15 ` [PATCH] Synaptics TouchPad driver for 2.5.70 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
2003-06-10 22:52 Joseph Fannin
2003-06-11 15:30 ` Joseph Fannin
2003-06-11 20:17 ` Andrew Morton
2003-06-11 20:29 ` Vojtech Pavlik
2003-06-11 22:12 ` Peter Osterlund
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=Pine.LNX.4.44.0306140045160.29353-100000@phoenix.infradead.org \
--to=jsimmons@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pebl@math.ku.dk \
--cc=vojtech@ucw.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 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).