On Mon, 2013-07-15 at 19:35 +0100, David Woodhouse wrote: > On Mon, 2013-07-15 at 11:09 -0700, Jordan Justen wrote: > > When the PM base address was moved from 0x400 to 0xb000, this > > code was missed. This prevented shutdown's via the UEFI system > > call from working. (For example, at the EFI shell prompt: reset -s) > > > > We now use gUefiOvmfPkgTokenSpaceGuid.PcdAcpiPmBaseAddress > > which is currently set at 0xb000. > > We'll end up getting this kind of information from the ACPI tables > provided by Qemu, won't we? And thus we won't have to remain in sync > with its hardware implementation quite so slavishly...
Well, today we are programming the address ourselves, so we need to at least be self-consistent. :) The future will probably only get more rocky, as we currently are claiming to support QEMU >= 0.10. Maybe if OVMF were bundled with QEMU and windows QEMU builds were up to date, then we might be able to tighten this window of support. -Jordan ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk _______________________________________________ edk2-devel mailing list edk2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/edk2-devel
