u-boot.lists.denx.de archive mirror
 help / color / mirror / Atom feed
From: Heinrich Schuchardt <xypron.glpk@gmx.de>
To: Jose Marinho <jose.marinho@arm.com>
Cc: ilias.apalodimas@linaro.org, sughosh.ganu@linaro.org,
	takahiro.akashi@linaro.org, agraf@csgraf.de, nd@arm.com,
	Samer El-Haj-Mahmoud <Samer.El-Haj-Mahmoud@arm.com>,
	Grant Likely <grant.likely@arm.com>,
	u-boot@lists.denx.de
Subject: Re: [PATCH 0/3] Conformance Profiles Table support in U-boot
Date: Fri, 17 Dec 2021 19:05:19 +0100	[thread overview]
Message-ID: <2c6d3e15-d8e9-71f5-f258-a7079fefcb87@gmx.de> (raw)
In-Reply-To: <20211217125506.138902-1-jose.marinho@arm.com>

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
>


  parent reply	other threads:[~2021-12-17 18:05 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-17 12:55 [PATCH 0/3] Conformance Profiles Table support in U-boot Jose Marinho
2021-12-17 12:55 ` [PATCH 1/3] efi: Create ECPT table Jose Marinho
2021-12-17 17:19   ` Heinrich Schuchardt
2021-12-23 15:01     ` Jose Marinho
2021-12-17 12:55 ` [PATCH 2/3] efi: ECPT add EBBRv2.0 conformance profile Jose Marinho
2021-12-17 17:26   ` Heinrich Schuchardt
2021-12-23 14:57     ` Jose Marinho
2021-12-23 18:31       ` Heinrich Schuchardt
2021-12-31 14:36         ` Jose Marinho
2022-01-01 23:56           ` Heinrich Schuchardt
2022-08-29 23:58             ` Heinrich Schuchardt
2021-12-17 12:55 ` [PATCH 3/3] cmd: efi: efidebug print ECPT table Jose Marinho
2021-12-17 13:29   ` Heinrich Schuchardt
2021-12-17 18:07   ` Heinrich Schuchardt
2021-12-23 14:59     ` Jose Marinho
2021-12-17 18:05 ` Heinrich Schuchardt [this message]
2021-12-23 15:20   ` [PATCH 0/3] Conformance Profiles Table support in U-boot Jose Marinho
2021-12-23 18:27     ` Heinrich Schuchardt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2c6d3e15-d8e9-71f5-f258-a7079fefcb87@gmx.de \
    --to=xypron.glpk@gmx.de \
    --cc=Samer.El-Haj-Mahmoud@arm.com \
    --cc=agraf@csgraf.de \
    --cc=grant.likely@arm.com \
    --cc=ilias.apalodimas@linaro.org \
    --cc=jose.marinho@arm.com \
    --cc=nd@arm.com \
    --cc=sughosh.ganu@linaro.org \
    --cc=takahiro.akashi@linaro.org \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).