linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Henrik Rydberg <rydberg@euromail.se>
To: Rafi Rubin <rafi@seas.upenn.edu>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	Chris Bagwell <chris@cnpbagwell.com>,
	Chase Douglas <chasedouglas@gmail.com>,
	Takashi Iwai <tiwai@suse.de>
Subject: Re: [PATCH] input: Introduce light-weight contact tracking
Date: Sun, 07 Nov 2010 21:50:57 +0100	[thread overview]
Message-ID: <4CD71131.3080706@euromail.se> (raw)
In-Reply-To: <4CD70FC0.6060503@seas.upenn.edu>

On 11/07/2010 09:44 PM, Rafi Rubin wrote:

> On 11/07/2010 03:18 PM, Henrik Rydberg wrote:
>> Some kernel drivers demand the use of contact tracking for proper
>> filtering and pointer emulation. With one exception, these drivers
>> are limited to a maximum of four concurrent contacts. This patch adds
>> a simple matcher for up to four contacts, with these notable properties:
> 
> Tracking in the ntrig driver needs to support a minimum of 6 fingers.  I have
> also seen press releases claiming 10+ eventually.  I don't know if those devices
> will support tracking in the hardware/firmware.


This is the exception I was talking about. The thing is, I can very well see a
driver supporting four fingers even if the device claims to support six. After
all, getting those four fingers working well will still be a big improvement.

Henrik

  reply	other threads:[~2010-11-07 20:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-07 20:18 [PATCH] input: Introduce light-weight contact tracking Henrik Rydberg
2010-11-07 20:44 ` Rafi Rubin
2010-11-07 20:50   ` Henrik Rydberg [this message]
2010-11-07 22:14 ` Rafi Rubin
2010-11-08 14:57   ` Henrik Rydberg
2010-11-08 16:54     ` Rafi Rubin
2010-11-08 19:07       ` Henrik Rydberg
2010-11-11  5:15         ` Rafi Rubin
2010-11-11 10:53           ` Henrik Rydberg
2010-11-11 20:00             ` Dmitry Torokhov

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=4CD71131.3080706@euromail.se \
    --to=rydberg@euromail.se \
    --cc=chasedouglas@gmail.com \
    --cc=chris@cnpbagwell.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafi@seas.upenn.edu \
    --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).