From: Ilias Apalodimas <ilias.apalodimas@linaro.org>
To: Michal Simek <michal.simek@amd.com>
Cc: u-boot@lists.denx.de, git@xilinx.com,
Algapally Santosh Sagar <santoshsagar.algapally@amd.com>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Leo Yu-Chi Liang <ycliang@andestech.com>,
Masahisa Kojima <masahisa.kojima@linaro.org>,
Shiji Yang <yangshiji66@outlook.com>,
Simon Glass <sjg@chromium.org>, Tom Rini <trini@konsulko.com>,
Venkatesh Yadav Abbarapu <venkatesh.abbarapu@amd.com>
Subject: Re: [PATCH] arm64: zynqmp: Do not describe u-boot.itb if SPL is disabled
Date: Tue, 5 Mar 2024 17:47:44 +0200 [thread overview]
Message-ID: <Zec-oE2mzj7Pngo3@hera> (raw)
In-Reply-To: <561f9d0ee96ebb6cd674042f269f280ab68fbbac.1708705118.git.michal.simek@amd.com>
On Fri, Feb 23, 2024 at 05:18:42PM +0100, Michal Simek wrote:
> There is no reason to describe u-boot.itb on system without SPL. Pretty
> much this is cover all systems which are using only boot.bin which contains
> all images inside.
>
> Signed-off-by: Michal Simek <michal.simek@amd.com>
> ---
>
> board/xilinx/common/board.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/board/xilinx/common/board.c b/board/xilinx/common/board.c
> index 9641ed307b75..4f38b7d27684 100644
> --- a/board/xilinx/common/board.c
> +++ b/board/xilinx/common/board.c
> @@ -43,7 +43,7 @@ struct efi_fw_image fw_images[] = {
> .image_index = 1,
> },
> #endif
> -#if defined(XILINX_UBOOT_IMAGE_GUID)
> +#if defined(XILINX_UBOOT_IMAGE_GUID) && defined(CONFIG_SPL_FS_LOAD_PAYLOAD_NAME)
What happens if this is defined with CONFIG_SPL_FS_LOAD_PAYLOAD_NAME="" ?
Cheers
/Ilias
> {
> .image_type_id = XILINX_UBOOT_IMAGE_GUID,
> .fw_name = u"XILINX-UBOOT",
> --
> 2.36.1
>
next prev parent reply other threads:[~2024-03-05 15:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 16:18 [PATCH] arm64: zynqmp: Do not describe u-boot.itb if SPL is disabled Michal Simek
2024-03-05 15:47 ` Ilias Apalodimas [this message]
2024-03-06 7:48 ` Michal Simek
2024-03-12 6:14 ` Ilias Apalodimas
2024-03-12 15:54 ` Michal Simek
2024-03-12 19:12 ` Ilias Apalodimas
2024-03-13 6:42 ` Michal Simek
2024-03-13 7:01 ` Ilias Apalodimas
2024-03-14 8:34 ` Ilias Apalodimas
2024-03-14 8:42 ` Michal Simek
2024-03-12 12:29 ` Heinrich Schuchardt
2024-03-12 15:25 ` Michal Simek
2024-03-22 11:57 ` Michal Simek
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=Zec-oE2mzj7Pngo3@hera \
--to=ilias.apalodimas@linaro.org \
--cc=git@xilinx.com \
--cc=masahisa.kojima@linaro.org \
--cc=michal.simek@amd.com \
--cc=santoshsagar.algapally@amd.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=venkatesh.abbarapu@amd.com \
--cc=xypron.glpk@gmx.de \
--cc=yangshiji66@outlook.com \
--cc=ycliang@andestech.com \
/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