From: Henrik Rydberg <rydberg@bitmath.org>
To: Chase Douglas <chase.douglas@canonical.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Chris Bagwell <chris@cnpbagwell.com>,
Takashi Iwai <tiwai@suse.de>,
Peter Hutterer <peter.hutterer@who-t.net>,
linux-input <linux-input@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Proposal for synaptics driver
Date: Tue, 12 Oct 2010 19:58:19 +0200 [thread overview]
Message-ID: <4CB4A1BB.9010006@bitmath.org> (raw)
In-Reply-To: <1286900585.22715.367.camel@mini>
On 10/12/2010 06:23 PM, Chase Douglas wrote:
[...]
> The rest of the
> touchpad is stationary and does not click. If no one has a better name
> for these touchpads, I'll refer to them as "integrated buttons"
> touchpads.
The name "integrated button" is the term in use for the later Macbook models,
where there is a button that clicks anywhere on the pad.
[...]
> My definition of a usable mouse is single touch and left
> click support (including click and drag using a physical button).
This has been stated several times already in related threads.
[...]
> For ClickPad devices, my feeling is that we should translate middle
> button clicks to left button clicks in the kernel, and MT+ST emulation
> should be performed. Middle and right click functionality may be
> provided for in userspace,
Having the physical click map to BTN_LEFT, regardless of where on the pad, and
flagging the presence of an integrated button via the version field in the
device id, would be consistent with existing drivers.
[...]
> I think we should disable single touch support over the buttons due to
> the following scenario:
>
> User positions cursor over button on screen, attempts to click physical
> touchpad button, cursor moves because of motion on touchpad when user
> depresses button.
The location and number of buttons could be freely mappable in userspace, so I
think we want to put minimum energy into the emulation part, considering it is
reworked in userspace anyways.
[...]
> Now the bit about integrated button touchpad detection. First, I would
> be interested in learning if anyone can disprove bit 0x200000 of the 0c
> extended caps flags means integrated buttons.
I think the easiest way to learn this is to produce a dkms package for people to
test.
Henrik
next prev parent reply other threads:[~2010-10-12 18:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-12 16:23 Proposal for synaptics driver Chase Douglas
2010-10-12 17:58 ` Henrik Rydberg [this message]
2010-10-12 19:26 ` Chase Douglas
2010-10-12 18:41 ` Chris Bagwell
2010-10-12 20:11 ` Chase Douglas
2010-10-12 20:23 ` Takashi Iwai
2010-10-12 21:11 ` Chris Bagwell
-- strict thread matches above, loose matches on Subject: below --
2010-10-13 3:16 Joey Lee
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=4CB4A1BB.9010006@bitmath.org \
--to=rydberg@bitmath.org \
--cc=chase.douglas@canonical.com \
--cc=chris@cnpbagwell.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.hutterer@who-t.net \
--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;
as well as URLs for NNTP newsgroup(s).