On Sun, 2013-01-20 at 19:54 -0800, Andrew Fish wrote: > The basic problem is as soon as the CSM calls something outside the > CSM code, then you don't know what kind of memory has been overwritten > or hardware written to. So the design was always it is not safe to > come back, as there is not a clean contract we can all agree to about > the system state. So that is the history.
Yes, absolutely. That part is clear enough. I'm talking about the case where we *haven't* called anything outside the CSM. We load the first sector from the boot drive, find that the 0xaa55 signature isn't there, and we *don't* jump to it. We return instead, as the spec says we should... and EDK2 doesn't cope with that. -- 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
