| commit | fd018e53384cc69faec15696d765caf93e303c79 | |
| author | tian, feng <eric_tian@tianocore.org> | |
| Mon, 9 Mar 2009 06:39:13 +0000 (9 06:39 +0000) | ||
| committer | tian, feng <eric_tian@tianocore.org> | |
| Mon, 9 Mar 2009 06:39:13 +0000 (9 06:39 +0000) | ||
| tree | 10cf62cdd8e46d19ab21ba432a13d1f2f0dd0981 | treesnapshot (tar.gz zip) |
| parent | cee06b34cbcefab3cec82cb030b0b8639d1767d4 | commitdiff |
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.
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.