From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/6] boot/arm-trusted-firmware: support 32bit Arm targets
Date: Thu, 14 Mar 2019 23:24:21 +0100 [thread overview]
Message-ID: <20190314232421.46ad28f2@windsurf> (raw)
In-Reply-To: <7f15bfd5388e2171b13b44722b84149d9f361551.1551866509.git.etienne.carriere@linaro.org>
Hello,
On Wed, 6 Mar 2019 11:11:35 +0100
Etienne Carriere <etienne.carriere@linaro.org> wrote:
> This change allows one to build the TF-A (Trusted Firmware A) for
> 32bit Armv7 and Armv8 platforms which arm-trusted-firmware supports
> since release v1.5.
>
> BR2_aarch64 is changed to BR2_ARM_CPU_ARMV8A as the later complemented
> by BR2_ARM_CPU_ARMV7A better represents to architectures that can
> support Arm Trusted Firmware A.
>
> When BR2_arm is enabled, TF-A is built in Aarch32 mode.
> Selection between Armv8-A (default) and Armv7-A (ARM_ARCH_MAJOR=7) is
> expected from BR2_TARGET_ARM_TRUSTED_FIRMWARE_ADDITIONAL_VARIABLES.
It seems a bit annoying to require passing ARM_ARCH_MAJOR=7 in those
additional variable. Why don't we do it automatically in
arm-trusted-firmware.mk. We have all the knowledge required, no?
> +ifeq ($(BR2_arm),y)
> +ARM_TRUSTED_FIRMWARE_MAKE_OPTS += ARCH=aarch32
Can we do:
ifeq ($(BR2_arm),y)
ARM_TRUSTED_FIRMWARE_MAKE_OPTS += ARCH=aarch32 ARM_ARCH_MAJOR=7
else
ARM_TRUSTED_FIRMWARE_MAKE_OPTS += ARCH=aarch64 ARM_ARCH_MAJOR=8
endif
for example ?
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-03-14 22:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 10:11 [Buildroot] [PATCH 1/6] boot/arm-trusted-firmware: support 32bit Arm targets Etienne Carriere
2019-03-06 10:11 ` [Buildroot] [PATCH 2/6] boot/arm-trusted-firmware: in-tree and OP-TEE BL32 Etienne Carriere
2019-03-06 10:11 ` [Buildroot] [PATCH 3/6] boot/arm-trusted-firmware: support debug mode Etienne Carriere
2019-03-06 10:11 ` [Buildroot] [PATCH 4/6] boot/arm-trusted-firmware: support alternate image files Etienne Carriere
2019-03-06 10:11 ` [Buildroot] [PATCH 5/6] configs/qemu_armv7a_tz_virt: Armv7-A emulation with TrustZone services Etienne Carriere
2019-03-06 10:11 ` [Buildroot] [PATCH 6/6] support/testing: test_optee.py: test optee boot and testsuite Etienne Carriere
2019-03-07 7:43 ` [Buildroot] [PATCH 1/6] boot/arm-trusted-firmware: support 32bit Arm targets Etienne Carriere
2019-03-14 22:24 ` Thomas Petazzoni [this message]
2019-03-15 9:00 ` Etienne Carriere
2019-03-18 7:22 ` Etienne Carriere
2019-03-19 6:50 ` 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=20190314232421.46ad28f2@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