On Mon, 2013-01-21 at 17:53 +0100, Paolo Bonzini wrote: > You are in control of the EFI_LEGACY_REGION_PROTOCOL implementation > though. If SeaBIOS needs 0xE0000-0xFFFFF to be always writable, just > make a Lock of that region a no-op...
We could do that, but it seems wrong to me. The LegacyRegion code is specific to the hardware, but should it really have SeaBIOS-specific hacks in it? I'd also have to hard-code the addresses, rather than picking them up from the CSM image. And it wouldn't allow us to grow the writeable UMB region dynamically. The code I sent last night handles it a lot more gracefully, and allows us to make full use of the whole of the UMB area. -- dwmw2
smime.p7s
Description: S/MIME cryptographic signature
------------------------------------------------------------------------------ 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. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122412
_______________________________________________ edk2-devel mailing list edk2-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/edk2-devel
