From: Henrik Rydberg <rydberg@euromail.se>
To: Takashi Iwai <tiwai@suse.de>,
Chase Douglas <chase.douglas@canonical.com>
Cc: linux-input@vger.kernel.org,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] Input: synaptics - multitouch and multifinger support
Date: Sun, 10 Oct 2010 09:49:45 +0200 [thread overview]
Message-ID: <4CB17019.7070002@euromail.se> (raw)
In-Reply-To: <s5hfwwg4p4t.wl%tiwai@suse.de>
Takashi, Chase,
talk about Heinz effect. :-)
Rather than taking any of the patches, I was wondering if we could get a single
patch including all the later findings and considerations on what devices should
have the multitouch mode. Also, unless there is a really really good reason for
it, without kernel parameters. After all, these patches should only add new
functionality without regressions.
Regarding the clickpad functionality, it is similar to the macbook pads with
integrated buttons, which has been implemented in userspace.
Regarding the tracking aspect of pointer emulation, Chase is completely right,
and this is a generic problem for several drivers. Tracking a single point by
picking the closest contact is a linear problem and could easily be performed in
interrupt context. I suggest we add it directly to the synaptics driver and then
revisit the question of adding generic tracking support to the kernel. Dmitry,
how does that sound to you?
Cheers,
Henrik
next prev parent reply other threads:[~2010-10-10 7:50 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-08 14:57 [PATCH 0/3] Input: synaptics - multitouch and multifinger support Chase Douglas
2010-10-08 14:57 ` [PATCH 1/3] Input: synaptics - add multitouch support Chase Douglas
2010-10-08 14:57 ` [PATCH 2/3] Input: synaptics - add multitouch multifinger support Chase Douglas
2010-10-08 14:58 ` [PATCH 3/3] Input: synaptics - remove touches over button click area Chase Douglas
2010-10-10 15:58 ` Chris Bagwell
2010-10-11 16:24 ` Chris Bagwell
2010-10-11 17:10 ` Takashi Iwai
2010-10-11 17:30 ` Dmitry Torokhov
2010-10-11 17:40 ` Takashi Iwai
2010-10-11 17:46 ` Chris Bagwell
2010-10-11 17:54 ` Henrik Rydberg
2010-10-11 18:29 ` Takashi Iwai
2010-10-10 15:44 ` [PATCH 2/3] Input: synaptics - add multitouch multifinger support Chris Bagwell
2010-10-10 15:37 ` [PATCH 1/3] Input: synaptics - add multitouch support Chris Bagwell
2010-10-10 15:41 ` Chris Bagwell
2010-10-08 16:37 ` [PATCH 0/3] Input: synaptics - multitouch and multifinger support Takashi Iwai
2010-10-08 16:38 ` Takashi Iwai
2010-10-08 17:48 ` Takashi Iwai
2010-10-08 17:15 ` Chase Douglas
2010-10-08 17:46 ` Takashi Iwai
2010-10-08 18:04 ` Dmitry Torokhov
2010-10-08 19:31 ` Takashi Iwai
2010-10-10 21:04 ` Dmitry Torokhov
2010-10-11 7:35 ` Takashi Iwai
2010-10-11 7:48 ` Henrik Rydberg
2010-10-11 7:59 ` Takashi Iwai
2010-10-11 13:41 ` Chris Bagwell
2010-10-11 14:01 ` Takashi Iwai
2010-10-11 14:24 ` Henrik Rydberg
2010-10-11 14:49 ` Takashi Iwai
2010-10-11 15:31 ` Henrik Rydberg
2010-10-11 15:58 ` Takashi Iwai
2010-10-10 7:49 ` Henrik Rydberg [this message]
2010-10-10 20:59 ` Dmitry Torokhov
2010-10-11 7:28 ` Takashi Iwai
2010-10-11 7:40 ` Henrik Rydberg
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=4CB17019.7070002@euromail.se \
--to=rydberg@euromail.se \
--cc=chase.douglas@canonical.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.de \
/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