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
..
Application	1. delete Include/Guid/VariableInfo.h	2009-02-27 05:35:08 +00:00
Bus	add check for invalid handle.	2009-03-04 04:31:46 +00:00
Core	1. retire the FvbServiceLib. Directly locating FVB protocol to access interfaces.	2009-03-09 06:39:13 +00:00
Include	Refine BaseMemoryTestLib and add instance with full functionality.	2009-03-06 03:34:25 +00:00
Library	Refine BaseMemoryTestLib and add instance with full functionality.	2009-03-06 03:34:25 +00:00
Logo	INF head modified	2008-12-12 01:27:36 +00:00
Universal	1. retire the FvbServiceLib. Directly locating FVB protocol to access interfaces.	2009-03-09 06:39:13 +00:00
ChangeLog.txt	Add change log for non-compatible change.	2007-11-20 07:34:25 +00:00
MdeModulePkg.dec	Refine BaseMemoryTestLib and add instance with full functionality.	2009-03-06 03:34:25 +00:00
MdeModulePkg.dsc	Refine BaseMemoryTestLib and add instance with full functionality.	2009-03-06 03:34:25 +00:00