diff options
author | Michael Kubacki <michael.kubacki@microsoft.com> | 2020-10-20 07:59:36 +0800 |
---|---|---|
committer | mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> | 2020-10-28 06:05:52 +0000 |
commit | 5550f4d33b64abc989ec6597ed6a19712b915c63 (patch) | |
tree | 5b2e078d32f8a78b037a8b399911d825f9f523b9 /BaseTools/Source/Python/Table/TableReport.py | |
parent | 2c1e9f1dc5efda0787d059cc1d5534a6c4409503 (diff) | |
download | edk2-5550f4d33b64abc989ec6597ed6a19712b915c63.tar.gz edk2-5550f4d33b64abc989ec6597ed6a19712b915c63.tar.bz2 edk2-5550f4d33b64abc989ec6597ed6a19712b915c63.zip |
FmpDevicePkg/FmpDxe: Add check image path Last Attempt Status capability
CheckTheImage() is currently used to provide the CheckImage()
implementation for the EFI_FIRMWARE_MANAGEMENT_PROTOCOL instance
produced by FmpDxe in addition to being called internally in the
SetImage() path.
Since CheckTheImage() plays a major role in determining the
validity of a given firmware image, an internal version of the
function is introduced - CheckTheImageInternal() that is capable
of returning a Last Attempt Status code to internal callers such
as SetTheImage().
The CheckImage() API as defined in the UEFI Specification for
EFI_FIRMWARE_MANAGEMENT_PROTOCOL is not impacted by this change.
CheckTheImageInternal() contains unique Last Attempt Status codes
during error paths in the function so it is easier to identify
the issue with a particular image through the Last Attempt Status
code value.
Cc: Liming Gao <gaoliming@byosoft.com.cn>
Cc: Michael D Kinney <michael.d.kinney@intel.com>
Cc: Guomin Jiang <guomin.jiang@intel.com>
Cc: Wei6 Xu <wei6.xu@intel.com>
Signed-off-by: Michael Kubacki <michael.kubacki@microsoft.com>
Acked-by: Liming Gao <gaoliming@byosoft.com.cn>
Reviewed-by: Wei6 Xu <wei6.xu@intel.com>
Reviewed-by: Michael D Kinney <michael.d.kinney@intel.com>
Diffstat (limited to 'BaseTools/Source/Python/Table/TableReport.py')
0 files changed, 0 insertions, 0 deletions