All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] boot/arm-trusted-firmware: use prebuilt BL33 images
Date: Thu, 29 Nov 2018 23:04:01 +0100	[thread overview]
Message-ID: <20181129230401.510c62a0@windsurf> (raw)
In-Reply-To: <1542900148-17204-1-git-send-email-etienne.carriere@linaro.org>

Hello Etienne,

On Thu, 22 Nov 2018 16:22:28 +0100, Etienne Carriere wrote:
> 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.
> 
> Signed-off-by: Etienne Carriere <etienne.carriere@linaro.org>
> ---
>  boot/arm-trusted-firmware/Config.in               | 22 +++++++++++++++++++++-
>  boot/arm-trusted-firmware/arm-trusted-firmware.mk |  4 ++++
>  2 files changed, 25 insertions(+), 1 deletion(-)

Thanks for this contribution. Could you explain the use case/rationale
for this change ? In which situation do you want to use prebuilt BL33
images, as opposed to having another Buildroot package that builds (or
downloads) them ?

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-11-29 22:04 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 [this message]
2018-11-30  9:53   ` Etienne Carriere
2018-12-01 20:18 ` Sergey Matyukevich
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=20181129230401.510c62a0@windsurf \
    --to=thomas.petazzoni@bootlin.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.