From: Luca Ceresoli via buildroot <buildroot@buildroot.org>
To: yann.morin@orange.com
Cc: Neal Frager <neal.frager@amd.com>, <buildroot@buildroot.org>,
<ibai.erkiaga-elorza@amd.com>, <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 v3 1/1] boot/xilinx-embeddedsw: only allow apps for device family
Date: Wed, 13 Aug 2025 11:27:55 +0200 [thread overview]
Message-ID: <20250813112755.63b17355@booty> (raw)
In-Reply-To: <aJxY+xaZhMFLzxX9@yd-6wlzhs3>
Hi Yann,
On Wed, 13 Aug 2025 11:20:59 +0200
yann.morin@orange.com wrote:
> Neal, All,
>
> On 2025-08-13 09:43 +0100, Neal Frager via buildroot spake thusly:
> > 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.
> >
> > 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.
> > ---
> > boot/xilinx-embeddedsw/Config.in | 5 ++++-
> > 1 file changed, 4 insertions(+), 1 deletion(-)
> >
> > diff --git a/boot/xilinx-embeddedsw/Config.in b/boot/xilinx-embeddedsw/Config.in
> > index 0dd6433608..96e9ca2fb0 100644
> > --- a/boot/xilinx-embeddedsw/Config.in
> > +++ b/boot/xilinx-embeddedsw/Config.in
> > @@ -5,7 +5,7 @@ comment "xilinx-embeddedsw needs a bare metal toolchain for tuple microblazeel-b
> >
> > menuconfig BR2_TARGET_XILINX_EMBEDDEDSW
> > bool "xilinx-embeddedsw"
> > - depends on BR2_aarch64
> > + depends on BR2_cortex_a53 || BR2_cortex_a72
>
> Note that (BR2_cortex_a53 || BR2_cortex_a72) is not a subset of
> BR2_aarch64; they can each be select when the target is BR2_arm,
> BR2_armeb or BR2_aarch64_be.
Ah, thanks for pointing out! I was indeed assuming that (a53 || a72) is
a subset of aarch64, or maybe (aarch64 || aarch64_be).
> So if xilinx-embeddedsw really is AArch64-LE, then you need to keep
> the dependency on BR2_aarch64. If it's really just AArch64, then you can
> relax it with a dependency on BR2_ARCH_IS_64 (plus the individual CPUs,
> of course).
AFAIK all the impacted Xilinx SoCs are aarch64, this that would become:
depends on BR2_aarch64 && (BR2_cortex_a53 || BR2_cortex_a72)
But I'll let Neal confirm or correct me.
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-13 9:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 8:43 [Buildroot] [PATCH v3 1/1] boot/xilinx-embeddedsw: only allow apps for device family Neal Frager via buildroot
2025-08-13 9:13 ` Luca Ceresoli via buildroot
2025-08-13 9:40 ` Frager, Neal via buildroot
2025-08-13 9:20 ` yann.morin
2025-08-13 9:27 ` Luca Ceresoli via buildroot [this message]
2025-08-13 9:44 ` Frager, Neal via buildroot
2025-08-13 10:00 ` yann.morin
2025-08-13 10:28 ` Frager, Neal via buildroot
2025-08-13 11:10 ` yann.morin
2025-08-13 11:46 ` Frager, Neal via buildroot
2025-08-13 13:31 ` Luca Ceresoli via buildroot
2025-08-13 14:22 ` Frager, Neal via buildroot
2025-08-13 14:41 ` Luca Ceresoli via buildroot
2025-08-13 15:28 ` Frager, Neal via buildroot
2025-08-13 16:15 ` Luca Ceresoli via buildroot
2025-08-14 5:27 ` Frager, Neal 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=20250813112755.63b17355@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox