From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] boot/arm-trusted-firmware: add new version
Date: Wed, 6 Feb 2019 09:40:42 +0100 [thread overview]
Message-ID: <20190206094042.101347d2@windsurf> (raw)
In-Reply-To: <20190205221414.23720-1-michal.lyszczek@bofc.pl>
On Tue, 5 Feb 2019 23:14:14 +0100
Micha? ?yszczek <michal.lyszczek@bofc.pl> wrote:
> config BR2_TARGET_ARM_TRUSTED_FIRMWARE_LATEST_VERSION
> + bool "Latest (v2.0)"
> +
> +config BR2_TARGET_ARM_TRUSTED_FIRMWARE_2_0
> + bool "v2.0"
> +
> +config BR2_TARGET_ARM_TRUSTED_FIRMWARE_1_4
> bool "v1.4"
This is not really what I suggested, but maybe I wasn't clear. I
suggested to do a similar thing to what we have for U-Boot:
- One option to select the latest stable
- One option to select an arbitrary stable version
See boot/uboot/Config.in:
choice
prompt "U-Boot Version"
help
Select the specific U-Boot version you want to use
config BR2_TARGET_UBOOT_LATEST_VERSION
bool "2018.09"
config BR2_TARGET_UBOOT_CUSTOM_VERSION
bool "Custom version"
help
This option allows to use a specific official versions
config BR2_TARGET_UBOOT_CUSTOM_TARBALL
bool "Custom tarball"
config BR2_TARGET_UBOOT_CUSTOM_GIT
bool "Custom Git repository"
config BR2_TARGET_UBOOT_CUSTOM_HG
bool "Custom Mercurial repository"
config BR2_TARGET_UBOOT_CUSTOM_SVN
bool "Custom Subversion repository"
endchoice
Also, if you're bumping the default ATF version from 1.4 to 2.0, it
should be a separate patch.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2019-02-06 8:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 22:14 [Buildroot] [PATCH] boot/arm-trusted-firmware: add new version Michał Łyszczek
2019-02-06 5:45 ` Baruch Siach
2019-02-06 8:45 ` michal.lyszczek at bofc.pl
2019-02-06 8:40 ` Thomas Petazzoni [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=20190206094042.101347d2@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox