linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Henrik Rydberg <rydberg@enmesh.se>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input <linux-input@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: input: mt: Software finger tracking in the kernel?
Date: Fri, 19 Mar 2010 11:58:35 +0100	[thread overview]
Message-ID: <4BA358DB.20708@enmesh.se> (raw)

Hi Dmitry,

there is an ongoing discussion about adding multitouch to X
(http://lists.x.org/archives/xorg-devel/2010-March/006206.html), which is
beginning to take on more solid form.

One of the suggestions emerging from that discussion is to add the software
finger tracking to the kernel. Back in summer 2009 when I thought about this, I
disregarded it as being too experimental. I have since then reconsidered,
starting to think it really is the right place.

The MT protocol allows applications to take advantage of multi-contact hardware,
but leaves the problems of finger tracking and filtering to the user. Arguably,
no application can make good use of MT without these, so the problem is pushed
forward, in this case to evdev or equivalent.

The knowledge of signal-to-noise ratios and prior input states resides in the
kernel. Because of this, the finger matching and filtering would naturally
reside within the kernel.

So, if there were to appear patches to include matching in the input core, would
you consider them? :-)

Cheers,
Henrik


             reply	other threads:[~2010-03-19 11:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-19 10:58 Henrik Rydberg [this message]
2010-03-19 11:38 ` input: mt: Software finger tracking in the kernel? Trilok Soni
2010-03-20  4:51 ` Ping Cheng
2010-03-20 19:27   ` Trilok Soni
2010-03-20 19:32     ` Ping Cheng
2010-03-20 19:44 ` Dmitry Torokhov
2010-03-20 21:59   ` Henrik Rydberg
2010-03-20 22:31   ` Henrik Rydberg
2010-03-21  3:06   ` Rafi Rubin

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=4BA358DB.20708@enmesh.se \
    --to=rydberg@enmesh.se \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@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).