From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Vincent Fazio <vfazio@xes-inc.com>
Cc: Sergey Matyukevich <geomatsi@gmail.com>,
"buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] [External] - [PATCH v2] boot/arm-trusted-firmware: Barebox available as BL33
Date: Tue, 21 Feb 2023 22:54:06 +0100 [thread overview]
Message-ID: <20230221225406.1bb8d63b@windsurf> (raw)
In-Reply-To: <PH1P110MB1603A4AA1638838DA56BAA069FDA9@PH1P110MB1603.NAMP110.PROD.OUTLOOK.COM>
Hello Vincent,
On Mon, 6 Feb 2023 13:36:09 +0000
Vincent Fazio <vfazio@xes-inc.com> wrote:
> Does TFA allow multiple BL33 images to be defined? I don't see a guard if some other package such as U-Boot or EDK2 has been enabled as well.
> If only one image is supported but multiple images are supplied via BL33 on the make command line, is it last declared wins?
This is absolutely true, so I have submitted
https://patchwork.ozlabs.org/project/buildroot/patch/20230221214904.454053-1-thomas.petazzoni@bootlin.com/
to move to a choice..endchoice in Config.in to select the BL33. Thanks
for reporting this!
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-02-21 21:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 18:30 [Buildroot] [PATCH] boot/arm-trusted-firmware: make Barebox available as BL33 Casey Reeves
2023-01-19 18:50 ` [Buildroot] [PATCH v2] boot/arm-trusted-firmware: " Casey Reeves
2023-02-06 13:36 ` [Buildroot] [External] - " Vincent Fazio
2023-02-21 21:54 ` Thomas Petazzoni via buildroot [this message]
2023-02-21 21:48 ` [Buildroot] " Thomas Petazzoni 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=20230221225406.1bb8d63b@windsurf \
--to=buildroot@buildroot.org \
--cc=geomatsi@gmail.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=vfazio@xes-inc.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