From: Chase Douglas <chasedouglas@gmail.com>
To: Christopher Heiny <christopherheiny@gmail.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>, linux-input@vger.kernel.org
Subject: Re: [PATCH 1/2] Input: synaptics - add second variant of two-button clickpad
Date: Tue, 13 Mar 2012 14:41:33 -0700 [thread overview]
Message-ID: <4F5FBF0D.8040106@gmail.com> (raw)
In-Reply-To: <1557704.NQD0apMTB1@brontomerus.synaptics.com>
On 03/01/2012 05:27 PM, Christopher Heiny wrote:
> On Thursday, March 01, 2012 05:18:34 PM Chase Douglas wrote:
>> On 03/01/2012 04:59 PM, Christopher Heiny wrote:
>>> Chase - those capability bits look a bit wacky to me. Can you tell me
>>> the TM number or product ID info for those pads?
>>
>> How do I get the TM number and product ID? What is the TM number?
>
> Sorry for the confusing terminology. TM number is the board number, found in
> query 0x01. Product ID is TouchPad model ID, found in query 0x00.
Sorry for not getting back sooner. Here's the Touchpad model line:
Touchpad model: 1, fw: 7.4, id: 0x1e0b1, caps: 0xd04713/0xa40000/0x2a0000
I don't see any usage of SYN_QUE_MODES, which is query 0x01. I can hack
it up, but I don't know what the returned data format is.
Thanks!
-- Chase
prev parent reply other threads:[~2012-03-13 21:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-14 4:21 [PATCH 1/2] Input: synaptics - add second variant of two-button clickpad Chase Douglas
2012-02-14 4:21 ` [PATCH 2/2] Input: synapticss - Set buttonpad property for all clickpads Chase Douglas
2012-02-20 10:48 ` [PATCH 1/2] Input: synaptics - add second variant of two-button clickpad Chase Douglas
2012-03-01 17:59 ` Chase Douglas
2012-03-01 19:45 ` Dmitry Torokhov
2012-03-02 0:59 ` Christopher Heiny
2012-03-02 1:18 ` Chase Douglas
2012-03-02 1:27 ` Christopher Heiny
2012-03-13 21:41 ` Chase Douglas [this message]
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=4F5FBF0D.8040106@gmail.com \
--to=chasedouglas@gmail.com \
--cc=christopherheiny@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@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 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).