linux-kernel - Re: [PATCH] input: mt: Identify pointer emulation contact

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 9 Dec 2010 15:49:21 -0800
From:	Dmitry Torokhov <dmitry.torokhov@...il.com>
To:	Henrik Rydberg <rydberg@...omail.se>
Cc:	Jiri Kosina <jkosina@...e.cz>, linux-input@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] input: mt: Identify pointer emulation contact

On Fri, Dec 10, 2010 at 12:19:05AM +0100, Henrik Rydberg wrote:
> For MT applications, the tracking id provides a robust way to know
> when a touch is new; essential information to determine when _not_ to
> emit motion events, for instance.  Currently, ST applications do not
> have the equivalent information, but instead rely on global properties
> such as a change in number of fingers. Moreover, some MT applications
> need to know which contact correponds to the pointer. This patch adds
> the ABS_TRACKING_ID axis and emits it in
> input_mt_report_pointer_emulation(), provided the proper absbit is
> setup by the driver.
> 

So how do you propose userspace will use it? Obviously it will not help
old dumb (ST) applications and new smart applications should understand
MT protocol and thus do not need to pay much attention to ST events
anyway. Apparently you have some new dumb userspace in mind here?

Thanks.

-- 
Dmitry
--
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/