From: Heinrich Schuchardt <xypron.glpk@gmx.de>
To: u-boot@lists.denx.de
Subject: [PATCH 1/2] efi: Add ESRT to the EFI system table
Date: Mon, 8 Feb 2021 23:18:03 +0100 [thread overview]
Message-ID: <c95fcdc0-8a6e-8f8b-f0d2-b93888c2afcc@gmx.de> (raw)
In-Reply-To: <20210208125246.32547-2-jose.marinho@arm.com>
On 2/8/21 1:52 PM, Jose Marinho wrote:
> The ESRT is initialised during efi_init_objlist after
> efi_initialize_system_table().
>
> The ESRT is initially created with size for 50 FW image entries.
> The ESRT is resized when it runs out of space. Every resize adds 50
> additional entries.
> The ESRT is populated from information provided by FMP instances only.
>
> Signed-off-by: Jose Marinho<jose.marinho@arm.com>
<josem> one limitation is, if any FMP instance is installed and then
uninstalled during the same boottime flow, the ESRT entries will not be
removed
<josem> this limitation is because I cannot find a proper UEFI way to
hook to a FMP protocol uninstall.
<xypron> register an event with RegisterProtocolNotify().
<xypron> EFI_CALL(efi_register_protocol_notify(...)) after exporting the
function in /include/efi_loader
<xypron> The event can be created with efi_create_event().
next prev parent reply other threads:[~2021-02-08 22:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 12:52 [PATCH 0/2] Add ESRT and test ESRT creation Jose Marinho
2021-02-08 12:52 ` [PATCH 1/2] efi: Add ESRT to the EFI system table Jose Marinho
2021-02-08 22:18 ` Heinrich Schuchardt [this message]
2021-02-08 22:30 ` Heinrich Schuchardt
2021-02-16 9:06 ` Heinrich Schuchardt
2021-02-16 10:27 ` Heinrich Schuchardt
2021-02-17 5:22 ` AKASHI Takahiro
2021-02-08 12:52 ` [PATCH 2/2] efi: ESRT cration unit test Jose Marinho
2021-02-17 5:26 ` AKASHI Takahiro
2021-02-19 18:04 [PATCHv2 0/2] Add ESRT and test ESRT creation Jose Marinho
2021-02-19 18:04 ` [PATCH 1/2] efi: Add ESRT to the EFI system table Jose Marinho
2021-02-20 17:31 ` Ilias Apalodimas
2021-02-21 9:08 ` 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=c95fcdc0-8a6e-8f8b-f0d2-b93888c2afcc@gmx.de \
--to=xypron.glpk@gmx.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.