On Sun, Jan 20, 2013 at 3:42 PM, David Woodhouse <dw...@infradead.org> wrote: > The main issue I have on the OVMF side is that it locks the entire > memory region from 0xC0000-0xFFFFF to be read-only, right before > invoking the Legacy16Boot method. This upsets SeaBIOS, which puts a > stack in the E0000 segment for use during hardware interrupts and other > calls which may otherwise overflow a caller's stack. There isn't > anywhere *else* it could put this stack, easily.
Is this still an issue? If so, why not use EBDA? I think it is extremely unlikely that EFI_COMPATIBILITY16_TABLE will be modified. -Jordan ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnnow-d2d _______________________________________________ edk2-devel mailing list edk2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/edk2-devel
