On 07/20/2012 02:03 AM, Daniel Kurtz wrote:
* Leave the device as SEMI_MT, but provide the real locations, and
allow userspace to determine the device vendor/model/etc. If
userspace knows that a specific device behaves in a specific way, it
can do its own quirking handling. Given the specificity
I'm trying to update the ati_remote module so that it is configurable
without having to change the source and recompile. I'm rather new to
kernel module development and was wondering how I should go about
creating an interface for configuration. My current implementation
creates a device node for c
On 07/18/2012 03:22 AM, Chung-yih Wang wrote:
The profile sensor clickpad in a Cr-48 Chromebook does a reasonable job of
tracking individual fingers. This tracking isn't perfect, but, experiments
show that it works better than just passing "semi-mt" data to userspace,
and making userspace try to
On 07/18/2012 08:02 PM, Chung-Yih Wang (王崇懿) wrote:
Hi Chase,
Thanks for your great comments. You are right, it is impossible to
get correct finger tracking if both fingers are moving. However, we
think it still worth to have the firmware tracking of the fingers as
they could perform well f
On 07/19/2012 10:05 AM, Daniel Kurtz wrote:
On Fri, Jul 20, 2012 at 12:16 AM, Chase Douglas
wrote:
On 07/18/2012 08:02 PM, Chung-Yih Wang (王崇懿) wrote:
Hi Chase,
Thanks for your great comments. You are right, it is impossible to
get correct finger tracking if both fingers are moving
5 matches
Mail list logo
