From: Luca Ceresoli via buildroot <buildroot@buildroot.org>
To: Neal Frager <neal.frager@amd.com>
Cc: yann.morin@orange.com, ibai.erkiaga-elorza@amd.com,
buildroot@buildroot.org, brandon.maier@collins.com, ju.o@free.fr,
thomas.petazzoni@bootlin.com, romain.naour@smile.fr,
michal.simek@amd.com, romain.naour@gmail.com
Subject: Re: [Buildroot] [PATCH v6 2/5] boot/xilinx-embeddedsw: only allow apps for device family
Date: Fri, 29 Aug 2025 11:02:18 +0200 [thread overview]
Message-ID: <20250829110218.4d19bc9f@booty> (raw)
In-Reply-To: <20250814052631.3412836-2-neal.frager@amd.com>
On Thu, 14 Aug 2025 06:26:28 +0100
Neal Frager <neal.frager@amd.com> wrote:
> This patch adds an architecture cpu dependency to each application to make
> sure that users can only build applications which are applicable to their
> target device family.
Generally speaking, git commit messages should use imperative tenses:
"This patch adds" -> "Add", etc.
I won't be nacking this patch just for this, but it would be nice for
the future.
> The versal_plm and versal_psmfw applications are specific to versal devices
> which are based on BR2_cortex_a72.
>
> The zynqmp_pmufw application is specific to zynqmp devices which are based on
> BR2_cortex_a53.
>
> Signed-off-by: Neal Frager <neal.frager@amd.com>
> ---
> V1->V2:
> - Replaced new family variant config option with an architecture cpu
> dependency, so no new configs are needed.
> - Updated patch title and commit message accordingly.
> V2->V3:
> - Changed package dependency to only appear if the cpu is BR2_cortex_a53
> or BR2_cortex_a72. This way, the xilinx-embeddedsw package will not
> appear with zero application options if another BR2_aarch64 cpu is
> selected.
> V3->V4:
> - Added BR2_TARGET_XILINX_EMBEDDEDSW_ARCH_SUPPORTS, so that all arch
> dependencies are in one place
> V4->V5:
> - Replace leading space copy paste error with tabs
> V5->V6:
> - Take advantage of BR2_TARGET_XILINX_FIRMWARE_ARCH_SUPPORTS from
> boot/Config.in to remove dependencies on BR2_aarch64.
> ---
> boot/xilinx-embeddedsw/Config.in | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/boot/xilinx-embeddedsw/Config.in b/boot/xilinx-embeddedsw/Config.in
> index 0dd6433608..3826f2e18e 100644
> --- a/boot/xilinx-embeddedsw/Config.in
> +++ b/boot/xilinx-embeddedsw/Config.in
> @@ -1,11 +1,9 @@
> comment "xilinx-embeddedsw needs a bare metal toolchain for tuple microblazeel-buildroot-elf"
> depends on BR2_TOOLCHAIN_BARE_METAL_BUILDROOT_ARCH != "microblazeel-buildroot-elf"
> - depends on BR2_aarch64
> depends on BR2_TOOLCHAIN_BARE_METAL_BUILDROOT
>
> menuconfig BR2_TARGET_XILINX_EMBEDDEDSW
> bool "xilinx-embeddedsw"
> - depends on BR2_aarch64
> depends on BR2_TOOLCHAIN_BARE_METAL_BUILDROOT
> help
> Build boot firmware applications from source for Xilinx
Shouldn't these two line removals be in patch 1?
Otherwise looks good.
Luca
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-08-29 9:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 5:26 [Buildroot] [PATCH v6 1/5] boot: add BR2_TARGET_XILINX_FIRMWARE_ARCH_SUPPORTS Neal Frager via buildroot
2025-08-14 5:26 ` [Buildroot] [PATCH v6 2/5] boot/xilinx-embeddedsw: only allow apps for device family Neal Frager via buildroot
2025-08-29 9:02 ` Luca Ceresoli via buildroot [this message]
2025-08-31 13:40 ` Frager, Neal via buildroot
2025-08-14 5:26 ` [Buildroot] [PATCH v6 3/5] boot/xilinx-prebuilt: only allow binaries " Neal Frager via buildroot
2025-08-14 5:26 ` [Buildroot] [PATCH v6 4/5] configs/versal_*: make savedefconfig cleaning Neal Frager via buildroot
2025-08-29 9:05 ` Luca Ceresoli via buildroot
2025-08-14 5:26 ` [Buildroot] [PATCH v6 5/5] boot/uboot: use BR2_TARGET_XILINX_FIRMWARE_ARCH_SUPPORTS Neal Frager via buildroot
2025-08-29 9:07 ` Luca Ceresoli via buildroot
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=20250829110218.4d19bc9f@booty \
--to=buildroot@buildroot.org \
--cc=brandon.maier@collins.com \
--cc=ibai.erkiaga-elorza@amd.com \
--cc=ju.o@free.fr \
--cc=luca.ceresoli@bootlin.com \
--cc=michal.simek@amd.com \
--cc=neal.frager@amd.com \
--cc=romain.naour@gmail.com \
--cc=romain.naour@smile.fr \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin@orange.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 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.