audk/MdeModulePkg/Universal
eric_tian 8a9e0b7274 1. retire the FvbServiceLib. Directly locating FVB protocol to access interfaces.
2. modify the method of getting right FVB protocol interface. move the notification event of FVB installation into variable driver. and also move ExitBootService event into variable driver.
3. use EFI_FVB2_WRITE_STATUS flag to distinct whether the FVB protocol supports writing operation or not.Currently, DxeCore installs FVB which has ~EFI_FVB2_WRITE_STATUS(that is, disable write) attrbiute. FvbRuntimeDxe driver should provide a full FVB protocol, which returns EFI_FVB2_WRITE_STATUS attribute to signify itself provide writable FVB protocol. So other modules which need write data by FVB protocol can locate it correctly.

git-svn-id: https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2@7835 6f19259b-4bc3-4df7-8a09-765794883524
2009-03-09 06:39:13 +00:00
..
CapsuleRuntimeDxe Update PeiCore to handle FvImage with PI FV extension header 2009-03-05 05:05:57 +00:00
Console Update ConPlatform to ensure console dev variable is correct. 2009-03-04 05:48:09 +00:00
DebugPortDxe
DebugSupportDxe retired PcdNtEmulatorEnable. 2009-03-04 02:10:20 +00:00
DevicePathDxe
Disk
DriverSampleDxe
EbcDxe
FaultTolerantWriteDxe Add full version FaultTolerantWrite Dxe driver. 2009-03-04 01:05:31 +00:00
HiiDatabaseDxe
MemoryTest/NullMemoryTestDxe
Metronome
MonotonicCounterRuntimeDxe
Network
PCD
PcatRealTimeClockRuntimeDxe
PcatSingleSegmentPciCfg2Pei
PlatformDriOverrideDxe
PrintDxe
SecurityStubDxe
SetupBrowserDxe
Variable 1. retire the FvbServiceLib. Directly locating FVB protocol to access interfaces. 2009-03-09 06:39:13 +00:00
WatchdogTimerDxe