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