Messages in this thread | | | Date | Tue, 17 Jul 2007 14:06:28 -0700 (PDT) | From | david@lang ... | Subject | Re: Hibernation considerations |
| |
On Tue, 17 Jul 2007, Jeremy Maitin-Shepard wrote:
> david@lang.hm writes: > > [snip] > >>>> * figure out which devices can wake up >>>> * put devices into low power states (wake-up devices are placed in the Dx >>>> states compatible with the wake capability, the others are powered off) > >> this can't be done by the image-saving kernel if that kernel doesn't know about >> the device. > > The image-saving kernel can be made to know about all of the "wake up" > devices; all other devices should have already been powered off by the > "hibernated" kernel.
not nessasarily.
for example, you don't want the "hibernated" kernel to spin down your disks in the general case, but your image-writing kernel may not have drivers in it to talk to some of the disks. when things are powered off this just isn't an issue, but if you use S4 mode instead it is.
David Lang - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |