On Sat, Feb 21, 2009 at 09:38:39PM +0100, Christian Franke wrote: >> >> But if the firmware already did, wouldn't this be a waste of boot time? >> >> > > Yes, it would. Most BIOS perform both health check and security freeze, > but some don't. For coreboot, it is not a waste of boot time. > > So if this is added to grub-mkconfig, it should be configurable by some > variable.
When using coreboot with GRUB, you usually have either: - A single GRUB, in chip, with a hand-crafted configuration. - Two GRUBs, one in chip which loads the other one from disk. The configuration for the first is hand-crafted but the second one would usually be grub-mkconfig'ed. In this case sounds like the right place for this would be the hand-crafted part. There's some example script code in: http://grub.enbug.org/CoreBoot How about adding it there? -- Robert Millan The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and how) you may access your data; but nobody's threatening your freedom: we still allow you to remove your data and not access it at all." _______________________________________________ Grub-devel mailing list Grub-devel@gnu.org http://lists.gnu.org/mailman/listinfo/grub-devel