From: Sergey Matyukevich <geomatsi@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] boot/arm-trusted-firmware: use prebuilt BL33 images
Date: Sat, 1 Dec 2018 23:18:34 +0300 [thread overview]
Message-ID: <20181201201834.GA7451@speedy.hunter> (raw)
In-Reply-To: <1542900148-17204-1-git-send-email-etienne.carriere@linaro.org>
Hello Etienne,
> This change allows one to build ATF with an externally built
> BL33 image or with the U-boot as BL33 boot stage.
>
> This change introduces a new configuration directive for TF-A to
> specify when BL33 stage is provided as a prebuilt image:
> BR2_TARGET_ARM_TRUSTED_FIRMWARE_PREBUILT_BL33.
>
> If BR2_TARGET_ARM_TRUSTED_FIRMWARE_PREBUILT_BL33 is enabled, the
> buildroot configuration shall specify the BL33 binary image location:
> BR2_TARGET_ARM_TRUSTED_FIRMWARE_BL33_IMAGE.
...
> --- a/boot/arm-trusted-firmware/Config.in
> +++ b/boot/arm-trusted-firmware/Config.in
> @@ -1,6 +1,6 @@
> config BR2_TARGET_ARM_TRUSTED_FIRMWARE
> bool "ARM Trusted Firmware (ATF)"
> - depends on BR2_aarch64 && BR2_TARGET_UBOOT
> + depends on BR2_aarch64
Could you please clarify why do you want to get rid of this dependency ?
IIUC so far all the arm64/atf boards supported by BR make use of U-Boot.
If you plan to use this feature for a board with any other type of
bootloader, then maybe it makes sense to add board config as well. In this
case other developers will be able at least build-test this particular
config swtich when testing their own ATF changes.
Regards,
Sergey
next prev parent reply other threads:[~2018-12-01 20:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-22 15:22 [Buildroot] [PATCH 1/1] boot/arm-trusted-firmware: use prebuilt BL33 images Etienne Carriere
2018-11-29 22:04 ` Thomas Petazzoni
2018-11-30 9:53 ` Etienne Carriere
2018-12-01 20:18 ` Sergey Matyukevich [this message]
2018-12-03 10:36 ` Etienne Carriere
2019-08-03 20:08 ` Thomas Petazzoni
2019-08-09 15:09 ` Etienne Carriere
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=20181201201834.GA7451@speedy.hunter \
--to=geomatsi@gmail.com \
--cc=buildroot@busybox.net \
/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.