linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chase Douglas <chase.douglas@canonical.com>
To: Henrik Rydberg <rydberg@bitmath.org>
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 15:26:50 -0400	[thread overview]
Message-ID: <1286911610.31864.38.camel@mini> (raw)
In-Reply-To: <4CB4A1BB.9010006@bitmath.org>

On Tue, 2010-10-12 at 19:58 +0200, Henrik Rydberg wrote:
> 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.

Ok, that sounds like the Synaptics ClickPad. An unfortunate name
clash :). How about "embedded buttons" touchpads?

> [...]
> 
> > 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.

Good idea, I'll make a dkms package when I've got some patches to test.

Thanks,

-- Chase


  reply	other threads:[~2010-10-12 19:27 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
2010-10-12 19:26   ` Chase Douglas [this message]
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=1286911610.31864.38.camel@mini \
    --to=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=rydberg@bitmath.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;
as well as URLs for NNTP newsgroup(s).