On Mon, Oct 18, 2010 at 10:19:37AM +0200, Corentin Chary wrote: > But if we do, we could add KEY_TOUCHPADTOGGLE 0x1b8 > Then bind it to XF86XK_TouchpadToggle (what's the right way to do that > ? keymaps ?) Yeah, we can add it to the X evdev map. That's not a problem. The only problem I see is that we don't have a good semantic definition - some machines send a toggle keycode, whereas others send on/off. That wouldn't in itself be a problem, but sometimes that's accompanied by the touchpad being disabled by the BIOS. In the latter case we probably don't want to map it, since the BIOS can do it anyway, but there's an argument that we need some way to expose that to userspace. -- Matthew Garrett | mjg59@xxxxxxxxxxxxx -- 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
