From: Rafi Rubin <rafi@seas.upenn.edu>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Henrik Rydberg <rydberg@enmesh.se>,
linux-input <linux-input@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: input: mt: Software finger tracking in the kernel?
Date: Sat, 20 Mar 2010 23:06:38 -0400 [thread overview]
Message-ID: <4BA58D3E.1000804@seas.upenn.edu> (raw)
In-Reply-To: <20100320194424.GC28402@core.coreip.homeip.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> I am not sure if input core itself is the proper place to do such
> thing, I'd envisioned something more like a library providing common
> code that drivers could opt in to use, like we hane ff-memless for
> memory-less force-feedback devices.
>
> Does it make any sense? I guess post the skeleton of the code and we can
> discuss further.
Regardless of where the code goes, I suggest we enable tracking by default for
MT devices and perhaps have a quirt MT_NOTRACK to opt out.
If tracking is the common case and expected down stream, it would be nice to let
HID compliant devices work without needing to explicitly identify them in code.
Rafi
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkuljTwACgkQwuRiAT9o60/iBwCgudrOvmam/A0VQ2uA0UtK5R3H
l3oAnAgEV7D+FFTWjofm85Djp25QhWq1
=2+sX
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2010-03-21 3:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-19 10:58 input: mt: Software finger tracking in the kernel? Henrik Rydberg
2010-03-19 11:38 ` Trilok Soni
2010-03-20 4:51 ` Ping Cheng
2010-03-20 19:27 ` Trilok Soni
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 [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=4BA58D3E.1000804@seas.upenn.edu \
--to=rafi@seas.upenn.edu \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rydberg@enmesh.se \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.