On Sat, 2010-05-22 at 12:38 +0200, Henrik Rydberg wrote: > Getting serious, it is anyone's guess what will happen next, but I was picturing > a table, with a large multitouch screen and buttons along the side of the table. > Sure, we can do "ABS_BTN_0", "ABS_BTN_1", etc, but with slots in place, it seems > more natural to use something like "ABS_MT_BTN_X". While at it, REL_MT event > makes sense for those touchscreen techniques which register changes, like > acoustic pulse recognition. Shouldn't this be handled in userspace? I don't think we want to be quirking drivers for instances where the same touchscreen is overlaid on buttons in some cases, but not in others. If we don't quirk, we'd need some mechanism to tell the driver about such buttons. -- Chase -- 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
