Tim, > Personally, I don't see this as a positive change. The PEI flow from the > earliest days has said: at the end of PEI there is memory and there is a > boot mode (see 11.2.1). You can see this assumption in 2.5 and 9.1 of > the PI specification, where the result of the PEI Foundation (not the > PEI phase) is "initialized permanent memory".
I think this reflects the history of PEI - it was developed first to initialize memory and then, "oh yeah, we need to find a place to do S3 resume". As such 2.5 makes no mention of S3 resume. 9.1 describes the handoff to the DXE Foundation and no one is arguing that you don't need permanent memory for that. > Making this change would change the contract between the PEI > Foundation and the DXE IPL. As such, it would break existing > implementations. This is relaxing the contract so a DXE IPL with the requirement of permanent memory (depex) would continue to work on both old and new implementations. From what I can see, the contract here is really between the Memory Init driver and the updated DXE IPL with the removal of the permanent memory PPI dependency. This change should be fully backwards compatible since existing Memory Init implementations that always publish permanent memory on S3 resume will continue to work. Can you elaborate on what gets broken? Thanks, Eugene _______________________________________________ edk2-devel mailing list edk2-devel@lists.01.org https://lists.01.org/mailman/listinfo/edk2-devel
