Skip to content

GitLab

Switch branch/tag
History Find file
Clone
Build: introduce per-BL CPPFLAGS and ASFLAGS
Masahiro Yamada authored 
Currently, BL*_CFLAGS and BL*_LDFLAGS are supported.

For completion, this adds BL*_CPPFLAGS and BL*_ASFLAGS.

My main motivation is to pass -D<macro> to BL*_CPPFLAGS so that
the macro can be used from all source files.

Change-Id: I0ca1e4e26386bef7fed999af140ee7cce7c2f8ef
Signed-off-by: default avatarMasahiro Yamada <yamada.masahiro@socionext.com>
848a7e8c
Name Last commit Last update
bl1 Factor xlat_table sections in linker scripts out into a header file
bl2 Factor xlat_table sections in linker scripts out into a header file
bl2u Factor xlat_table sections in linker scripts out into a header file
bl31 Merge changes from topic "mp/enhanced_pal_hw" into integration
bl32 Bug fix: Protect TSP prints with lock
common Fix crash dump for lower EL
docs Merge "Changelog updates for recent commits" into integration
drivers Merge changes from topic "ddr_map" into integration
fdts corstone700: updating the kernel arguments to support initramfs
include FVP: Add BL2 hash calculation in BL1
lib fconf: notify if fw_config dt is not used
make_helpers Build: introduce per-BL CPPFLAGS and ASFLAGS
plat Merge "plat/sgm775: Add support for dynamic config using fconf" into integration
services spd: tlkd: support new TLK SMCs for RPMB service
tools Merge changes from topic "sb/dualroot" into integration
.checkpatch.conf Re-apply GIT_COMMIT_ID check for checkpatch
.editorconfig doc: Final, pre-release fixes and updates
.gitignore Ignore the ctags file
.gitreview Add a .gitreview file for convenience
Makefile FVP: Add BL2 hash calculation in BL1
dco.txt Drop requirement for CLA in contribution.md
license.rst doc: De-duplicate readme and license files
readme.rst doc: Formatting fixes for readme.rst
readme.rst

Trusted Firmware-A

Trusted Firmware-A (TF-A) is a reference implementation of secure world software for Arm A-Profile architectures (Armv8-A and Armv7-A), including an Exception Level 3 (EL3) Secure Monitor. It provides a suitable starting point for productization of secure world boot and runtime firmware, in either the AArch32 or AArch64 execution states.

TF-A implements Arm interface standards, including:

The code is designed to be portable and reusable across hardware platforms and software models that are based on the Armv8-A and Armv7-A architectures.

In collaboration with interested parties, we will continue to enhance TF-A with reference implementations of Arm standards to benefit developers working with Armv7-A and Armv8-A TrustZone technology.

Users are encouraged to do their own security validation, including penetration testing, on any secure world code derived from TF-A.

More Info and Documentation

To find out more about Trusted Firmware-A, please view the full documentation that is available through trustedfirmware.org.

Copyright (c) 2013-2019, Arm Limited and Contributors. All rights reserved.