> > Ok, maybe not to so easy after all, which probably answers my own > > question. Looks like a EVIOCGMTSLOT, taking both slot and event code > > as argument, would be the cleaner route to take. Another ioctl, how do we > > feel about that? > > What's the problem with userspace locking? The idea was to get by without it. Regarding ioctls, it does not seem realizable due to ioctl number exhaustion. A sysfs interface for all EV_ABS and per-slot MT values could be a more future-proof alternative. 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
