On Fri, 2008-03-21 at 14:17 +0100, Pavel Machek wrote:I see a problem here. This could work. And if it is successful, the "kexec reboot around busted hw"-trick
So what's the reason for pushing for this insanely-early workaround in the first place, instead of letting user-space do something likeYou have interpretted code runing (AML), and you want to replace it
cat my-dsdt-image > /proc/sys/acpi/DSDT
or whatever at runtime?
with different code?
Akin to changing from one kernel to different during runtime?
Heh. That gave me an idea.
Can we use kexec for this? Let's say you get as far in boot as the
initrd and realize that you're running on one of these screwed up
systems. Can you stick the new DSDT somewhere known (and safe) in
memory, and kexec yourself back to the beginning of the kernel boot?
When you boot up the second time, you have the new, shiny DSDT there
which is, of course, used instead of the bogus BIOS one.