Hi, I think it's better for the kernel to send event to user space and the tracking would be done inside a daemon where we can add also other features than tracking. Many differences exist for MT devices, some do the tracking inside the firmware others don't, so maybe a user space daemon can handle all this. Isn't all this similar to touchpads that present a very non stable input when used directly and where we add after in the stack a module/function to remove the shaking (I think in X) ? What you think about that ? ik. On Thu, Jun 10, 2010 at 3:00 AM, Rafi Rubin <rafi@xxxxxxxxxxxxxx> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Now that Henrik's slots seem to be coming along, I'd like to see what people > think about in kernel contact tracking. > > I'd certainly like to see it available for hid-ntrig, but would rather see the > centralized code to make it available to all the devices lacking or with poor > tracking. > > Any objection on general principles, or would this simply be a matter of getting > it right? > > > Cheers, > Rafi > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.10 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iEYEARECAAYFAkwQOTsACgkQwuRiAT9o60/ADQCeJMOK9sLcyN0CNcEeSFvEY1Xc > GFsAoLkC6PvzZjrQfWjQC1qcgmBExpjn > =y+qv > -----END PGP SIGNATURE----- > -- > To unsubscribe from this list: send the line "unsubscribe linux-input" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
