From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Casey Reeves <casey@xogium.me>
Cc: Sergey Matyukevich <geomatsi@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v2] boot/arm-trusted-firmware: Barebox available as BL33
Date: Tue, 21 Feb 2023 22:48:40 +0100 [thread overview]
Message-ID: <20230221224840.668f2559@windsurf> (raw)
In-Reply-To: <20230119185041.3430421-1-casey@xogium.me>
On Thu, 19 Jan 2023 19:50:40 +0100
Casey Reeves <casey@xogium.me> wrote:
> Since version 2022.04.0, Barebox now support a generic image built for
> platforms, to be used as BL33 to generate FIP images. This patch makes
> it available as choice of BL33 to be used with ATF and is based on the
> similar work put into U-Boot as BL33.
>
> Signed-off-by: Casey Reeves <casey@xogium.me>
>
> ---
> Changes v1 -> v2:
> - fixed quoting issue in the default image name
> ---
> boot/arm-trusted-firmware/Config.in | 21 +++++++++++++++++++
> .../arm-trusted-firmware.mk | 6 ++++++
> 2 files changed, 27 insertions(+)
Applied to next, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-02-21 21:48 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
2023-02-21 21:48 ` Thomas Petazzoni via buildroot [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=20230221224840.668f2559@windsurf \
--to=buildroot@buildroot.org \
--cc=casey@xogium.me \
--cc=geomatsi@gmail.com \
--cc=thomas.petazzoni@bootlin.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