well I guess it depends on philosophy. if the idea is to have minimalistic bios then ability to suspend doesn't belong there.
on the other hand some configurations of "bios" (where "bios" would be the thing in the thing in FLASH), often include linux kernel and that alone could be re-used to enable suspend. Although the proper way to do this is probably to use "management mode" of the recent CPUs.
On Fri, 14 May 2004 firstname.lastname@example.org wrote:
If the hibernation restore occurred from the BIOS, then one wouldn't need to boot from disk, right? Also, if you don't need to boot from disk, the BIOS could restore the entire memory state and then re-initialize any peripherals that need it (PCI, PCMCIA, CF, VGA, etc.) Should be quicker, elegant, and more effective, right? (and OS independent if done right.)
Question is, how much memory does LinuxBIOS use for itself? We'd have to make sure that it doesn't "step on its own feet" trying to get the memory state loaded.
From Adam Sulmicki email@example.com on 14 May 2004:
I don't really think it is BIOS issue.
OS can do it just fine on its own. I don't see why BIOS should be invovled here.
Has any work been done toward the goal of "Hibernation"? I'm writing
the type that would use a separate partition equal to ram + swap space to store the current memory state. If no one has done any work to
effect, how difficult would it be? I may be willing to help the
I've never programmed for a BIOS, but I've done mmap() stuff before.
Linuxbios mailing list Linuxbios@clustermatic.org http://www.clustermatic.org/mailman/listinfo/linuxbios