On Fri, Apr 5, 2013 at 3:06 PM, Duane Voth <[email protected]> wrote: > Mike, this is with qemu 1.2.0 and OVMF from svn rev 14243 (a week or so > old).
I think these should work fine together. I just booted my build of OVMF with 1.2.0. > The looping code is reading i/o port 0x408 and getting 0xffffffff, Don't we set PcdAcpiPmBaseAddress to 0xB000 in OvmfPkg/OvmfPkg.dec? I wonder how 0x400+8 is coming into the picture. Hmm... I see PcdPerfPkgAcpiIoPortBaseAddress uses 0x400 in PerformancePkg/PerformancePkg.dec. Maybe we need to set this to 0xB000 in the OVMF .dsc. > My > Build/OvmfX64/DEBUG_GCC46/X64/OvmfPkg/Sec/SecMain/OUTPUT/SecMain.map has > _gPcd_FixedAtBuild_PcdAcpiPmBaseAddress at 0x000104f8 I think 0x000104f8 is the address where the PCD variable is located, not what is being used for the PCD. >, but gdb reports zeros > for 16 bytes at both those locations as well as 0xB000. 0x400/0xB000 are I/O ranges, not memory ranges. > Seems as if acpi > emulation in qemu is disabled but I'm running qemu from a command line: > > $ qemu-system-x86_64 -m 1024 -bios OVMF.fd -S -s -monitor stdio I also booting using those flags. It booted after telling the monitor to run by using the c command at the monitor prompt due to the -S qemu flag being used. -Jordan ------------------------------------------------------------------------------ Minimize network downtime and maximize team effectiveness. Reduce network management and security costs.Learn how to hire the most talented Cisco Certified professionals. Visit the Employer Resources Portal http://www.cisco.com/web/learning/employer_resources/index.html _______________________________________________ edk2-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/edk2-devel
