From: Michal Simek <michal.simek@amd.com>
To: Mike Looijmans <mike.looijmans@topic.nl>, u-boot@lists.denx.de
Cc: Marek Vasut <marek.vasut+renesas@mailbox.org>,
Simon Glass <sjg@chromium.org>, Tom Rini <trini@konsulko.com>
Subject: Re: [PATCH] xilinx: Allow alternative boot strategies in zynq-common.h
Date: Mon, 17 Mar 2025 10:42:34 +0100 [thread overview]
Message-ID: <b0e2ffae-a198-42a3-82ec-ec09d466047b@amd.com> (raw)
In-Reply-To: <20250307062948.216102-1-mike.looijmans@topic.nl>
On 3/7/25 07:29, Mike Looijmans wrote:
> Allow config headers that include zynq-common.h to provide their own
> (distro) boot strategies. This is implemented by skipping the section
> when BOOT_ENV has already been defined.
>
> Signed-off-by: Mike Looijmans <mike.looijmans@topic.nl>
> ---
>
> include/configs/zynq-common.h | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/include/configs/zynq-common.h b/include/configs/zynq-common.h
> index 37c77aa1611..ad872c9d922 100644
> --- a/include/configs/zynq-common.h
> +++ b/include/configs/zynq-common.h
> @@ -48,6 +48,9 @@
> #define BOOTENV
> #else
>
> +/* Only use this section if no BOOTENV has been configured yet */
> +#ifndef BOOTENV
> +
> #ifdef CONFIG_CMD_MMC
> #define BOOT_TARGET_DEVICES_MMC(func) func(MMC, mmc, 0) func(MMC, mmc, 1)
> #else
> @@ -167,6 +170,9 @@
> BOOT_TARGET_DEVICES_DHCP(func)
>
> #include <config_distro_bootcmd.h>
> +
> +#endif /* BOOTENV */
> +
> #endif /* CONFIG_XPL_BUILD */
>
> /* Default environment */
Just for the record v2 was sent.
M
prev parent reply other threads:[~2025-03-17 9:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1b153bce-a66a-45ee-a5c6-963ea6fb1c82.949ef384-8293-46b8-903f-40a477c056ae.b6aa62ed-c125-4ac0-8424-d1beba536b58@emailsignatures365.codetwo.com>
2025-03-07 6:29 ` [PATCH] xilinx: Allow alternative boot strategies in zynq-common.h Mike Looijmans
2025-03-17 9:42 ` 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=b0e2ffae-a198-42a3-82ec-ec09d466047b@amd.com \
--to=michal.simek@amd.com \
--cc=marek.vasut+renesas@mailbox.org \
--cc=mike.looijmans@topic.nl \
--cc=sjg@chromium.org \
--cc=trini@konsulko.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