On Wed, Jul 11, 2007 at 10:53:35AM +1000, Nigel Cunningham wrote: > On Wednesday 11 July 2007 10:45:50 Matthew Garrett wrote: > > How are you going to shift into suspend to disk without going via > > userspace? It's quite plausible that people will want different > > configuration at that point (or, realistically, need a different set of > > workarounds...) > > This is done after writing the image, from kernel space. We do the > suspend-to-ram, and if/when we wake from that, we look at the lid switch > state before removing the image. If it's still closed, the kernel code powers > down again (this time properly) without userspace ever seeing the light of > day. Yes. I'm sort of struggling to see how this is done especially reliably - if we have separate hibernation and suspend to ram pathways, which is executed in this scenario? -- Matthew Garrett | mjg59@xxxxxxxxxxxxx - 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
