Hi Peter, > it wasn't the first reaction. it was the third, after we hacked up > synaptics [1], then libinput [2], both rather unsatisfactory. Not sure what > chromeos does but they'll probably would need similar code. And any other > users of the evdev API of course. So if this approach did not work very well in userland, why would it work any better in the kernel? Henrik -- 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