I see that more and more drivers are adding callbacks for the PI-defined EndOfDxe event group. However, none of the EDK2 implementations signal this event group. As a result, we are seeing widely varying implementations as to its placement, and a lot of assumptions about what is completed at that point. For example, is PCI enumeration complete? IMO, you can't assume that because no UEFI devices have been connected. As the PI spec says: " Prior to invoking any UEFI drivers, applications, or connecting consoles, the platform should signal the event EFI_END_OF_DXE_EVENT_GUID."
So it seems appropriate that the signaling of this event should be immediately upon calling the BdsEntry() function in BdsDxe. Thoughts? Tim ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available. Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ edk2-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/edk2-devel
