| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <4BA358DB.20708@enmesh.se> Date: Fri, 19 Mar 2010 11:58:35 +0100 From: Henrik Rydberg <rydberg@...esh.se> To: Dmitry Torokhov <dmitry.torokhov@...il.com> CC: linux-input <linux-input@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: input: mt: Software finger tracking in the kernel? 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists