U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Simek <michal.simek@amd.com>
To: Padmarao Begari <padmarao.begari@amd.com>, u-boot@lists.denx.de
Cc: git@amd.com
Subject: Re: [PATCH] board: xilinx: Update ESRT after copying GUID
Date: Wed, 26 Nov 2025 09:08:23 +0100	[thread overview]
Message-ID: <98d68ebe-15dd-49aa-964f-e235f19cce12@amd.com> (raw)
In-Reply-To: <20251104125725.1628068-1-padmarao.begari@amd.com>



On 11/4/25 13:57, Padmarao Begari wrote:
> The EFI System Resource Table (ESRT) is updated after the firmware
> image GUID is copied to the fw_images structure. This ensures that
> the ESRT accurately reflects the current firmware resources.
> 
> Signed-off-by: Padmarao Begari <padmarao.begari@amd.com>
> ---
>   board/xilinx/common/board.c | 11 +++++++++++
>   1 file changed, 11 insertions(+)
> 
> diff --git a/board/xilinx/common/board.c b/board/xilinx/common/board.c
> index 26facb6daea..ab50a795e6b 100644
> --- a/board/xilinx/common/board.c
> +++ b/board/xilinx/common/board.c
> @@ -766,6 +766,17 @@ int fwu_platform_hook(struct udevice *dev, struct fwu_data *data)
>   	/* Copy image type GUID */
>   	memcpy(&fw_images[0].image_type_id, &img_entry->image_type_guid, 16);
>   
> +	if (IS_ENABLED(CONFIG_EFI_ESRT)) {
> +		efi_status_t ret;
> +
> +		/* Rebuild the ESRT to reflect any updated FW images. */
> +		ret = efi_esrt_populate();
> +		if (ret != EFI_SUCCESS) {
> +			log_warning("ESRT update failed\n");
> +			return ret;
> +		}
> +	}
> +
>   	return 0;
>   }
>   

Applied.
M

      reply	other threads:[~2025-11-26  8:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-04 12:57 [PATCH] board: xilinx: Update ESRT after copying GUID Padmarao Begari
2025-11-26  8:08 ` Michal Simek [this message]

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=98d68ebe-15dd-49aa-964f-e235f19cce12@amd.com \
    --to=michal.simek@amd.com \
    --cc=git@amd.com \
    --cc=padmarao.begari@amd.com \
    --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