On Wednesday 28 June 2006 3:16 pm, Pavel Machek wrote: > > ...but leaving machine "suspended" with display running (and > pressumably keyboard still reactive to keypresses) is really a bit > different from "normal" suspend-to-RAM. Keyboard reactive is just normal wakeup event processing. Of course, we have pretty lousy support for wakeup events in Linux just now. :( Although I'm glad to say that at least for USB, wakeup events are basically working, and the main gaps are in platform support (which unfortunately includes ACPI). It would still be nice to see things like non-USB keyboards and mice be wakeup event sources though. And of course, S1 and S3 states working ... > Yes, S1 is probably right description of above state. IIRC I seen > machines that left dispaly ON in S1... I don't seem to recall seeing the ACPI spec laying down requirements about displays. Those should be platform-specific. That would be epecially true of non-ACPI systems, which get to define "standby" and "STR" states to suit. (And I'd kind of hope the system that Jim sketched isn't relying on ACPI!) - Dave
