On Wed, 2014-05-21 at 09:52 -0400, Kevin O'Connor wrote: > > Why is it wrong to declare memory at 0xef000-0xf0000 and have a stack > at 0xef520-0xefd20?
I found the problem and it was on the UEFI side, not with the SeaBIOS patch. UEFI was only unlocking the requested 0xef000-0xf0000 region when it actually issued a Legacy16Boot request. Prior to that, the entire 0xc0000-0x100000 region was remaining locked. I'll fix my EDK2 patch accordingly. -- David Woodhouse Open Source Technology Centre david.woodho...@intel.com Intel Corporation
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ SeaBIOS mailing list SeaBIOS@seabios.org http://www.seabios.org/mailman/listinfo/seabios
