From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/8] arm-trusted-firmware: add option to enable/disable building FIP image
Date: Fri, 08 Dec 2017 13:34:56 +0100 [thread overview]
Message-ID: <878ted1jpr.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20171203214811.3124-2-thomas.petazzoni@free-electrons.com> (Thomas Petazzoni's message of "Sun, 3 Dec 2017 22:48:04 +0100")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
> Currently, our arm-trusted-firmware unconditionally builds a FIP
> (Firmware Image Package). While this is often needed on platforms
> where ATF encapsulates U-Boot, it is not the case on some other
> platforms where it's U-Boot that encapsulates parts of ATF.
> In order to prepare the support for the later platforms, we make
> building the FIP image optional, and update the only defconfig we have
> that uses ARM Trusted Firmware.
> Note: we considered adding a "default y" here to preserve backward
> compatibility, but there really isn't any default that is sane:
> whether a FIP image needs to be built or not is purely platform
> specific.
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Committed, thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2017-12-08 12:34 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-03 21:48 [Buildroot] [PATCH 0/8] Improve ATF to support additional platforms Thomas Petazzoni
2017-12-03 21:48 ` [Buildroot] [PATCH 1/8] arm-trusted-firmware: add option to enable/disable building FIP image Thomas Petazzoni
2017-12-04 21:10 ` Sergey Matyukevich
2017-12-06 16:09 ` Danomi Manchego
2017-12-08 9:14 ` Peter Korsgaard
2017-12-08 12:34 ` Peter Korsgaard [this message]
2017-12-03 21:48 ` [Buildroot] [PATCH 2/8] arm-trusted-firmware: add BR2_TARGET_ARM_TRUSTED_FIRMWARE_UBOOT_AS_BL33 Thomas Petazzoni
2017-12-08 12:35 ` Peter Korsgaard
2017-12-03 21:48 ` [Buildroot] [PATCH 3/8] arm-trusted-firmware: allow to generate the BL31 image Thomas Petazzoni
2017-12-06 16:28 ` Jagan Teki
2017-12-08 12:35 ` Peter Korsgaard
2017-12-03 21:48 ` [Buildroot] [PATCH 4/8] uboot: add support for bundling ATF BL31 into U-Boot Thomas Petazzoni
2017-12-06 16:29 ` Jagan Teki
2017-12-08 12:37 ` Peter Korsgaard
2017-12-08 12:46 ` Thomas Petazzoni
2017-12-03 21:48 ` [Buildroot] [PATCH 5/8] mv-ddr-marvell: new package Thomas Petazzoni
2017-12-08 12:42 ` Peter Korsgaard
2017-12-08 13:18 ` Thomas Petazzoni
2017-12-03 21:48 ` [Buildroot] [PATCH 6/8] binaries-marvell: " Thomas Petazzoni
2017-12-04 20:17 ` Sergey Matyukevich
2017-12-03 21:48 ` [Buildroot] [PATCH 7/8] atf: add support for Marvell Armada SoCs Thomas Petazzoni
2017-12-08 17:59 ` Peter Korsgaard
2017-12-03 21:48 ` [Buildroot] [PATCH 8/8] support/testing: add tests for ATF Thomas Petazzoni
2017-12-04 20:33 ` Sergey Matyukevich
2017-12-08 18:02 ` Peter Korsgaard
2017-12-11 13:00 ` Thomas Petazzoni
2017-12-11 18:59 ` Peter Korsgaard
2017-12-06 16:26 ` [Buildroot] [PATCH 0/8] Improve ATF to support additional platforms Jagan Teki
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=878ted1jpr.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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.