On Sat, Mar 7, 2009 at 8:26 PM, Matthew Garrett <mjg59@xxxxxxxxxxxxx> wrote: > On Sat, Mar 07, 2009 at 08:19:51PM +0000, Richard Hughes wrote: > >> Mapping KEY_SUSPEND to hibernate is just insane. Can you please change >> the toshiba driver to use KEY_HIBERNATE and KEY_SUSPEND as thinkpad >> now does? Thanks. > > Mapping KEY_SUSPEND to hibernate is what we've been doing for years. > It's what hal *still does*. Sure, but how much userspace now listens to HAL for these events? Xorg and evdev has taken over that role for all the session. We can ship a trivial patch as an fdi file to HAL to remap this if required. > KEY_SLEEP has been the suspend to RAM key forever. Except if you're a USB keyboard. Grep through the kernel sources and see how many drivers get this wrong. We can't map three sleep states to two buttons in any sane way. For instance, is the sleep acpi button supposed to trigger a suspend of hibernate? Surely this is user policy as it is not specified on the the exterior of the machine. > How are we supposed to perform this transition? We've no idea > how much of userspace makes the same assumption. FWIW, I think emitting KEY_ events (not switch events) in HAL is crazy as now we can just use the fixed Xorg in the session. FWIW, HAL gets other keys wrong too, for instance KEY_BATTERY is mapped to display_off, but nobody has noticed as we've been using Xorg since ages. Richard. -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
