On 12/17/21 13:55, Jose Marinho wrote:
The Conformance Profiles Table (ECPT) table will be included in the UEFI
specification 2.9+.
The change suggested in
https://bugzilla.tianocore.org/show_bug.cgi?id=3591
is a not well designed: How could the missing of a table ever be taken
as a sign of compliance?
How would an application make use of the table?
What information does it provide that is not better obtained from API calls?
As the table is not defined in UEFI 2.9 and no software uses it, why
should we implement it?
Best regards
Heinrich
The ECPT table was introduced in UEFI following the code-first path. The
acceptance ticket can be viewed at:
https://bugzilla.tianocore.org/show_bug.cgi?id=3591
This patch set implements the ECPT table in U-boot.
Jose Marinho (3):
efi: Create ECPT table
efi: ECPT add EBBRv2.0 conformance profile
cmd: efi: efidebug print ECPT table
cmd/efidebug.c | 45 +++++++++++++++++++
include/efi_api.h | 14 ++++++
include/efi_loader.h | 9 ++++
lib/efi_loader/Kconfig | 12 +++++
lib/efi_loader/Makefile | 1 +
lib/efi_loader/efi_conformance.c | 75 ++++++++++++++++++++++++++++++++
lib/efi_loader/efi_setup.c | 6 +++
7 files changed, 162 insertions(+)
create mode 100644 lib/efi_loader/efi_conformance.c
