tools: Get the tool's binary name from the main makefile
Manish V Badarkhe authored
Currently, the tool's makefile override the tool's binary name
which is already been defined in the main makefile.
Hence fix is provided so that the tool's makefile get the tool's
binary name from the main makefile instead of overriding it.

Change-Id: I8af2bd391a96bba2dbcddef711338a94ebf5f038
Signed-off-by: default avatarManish V Badarkhe <Manish.Badarkhe@arm.com>
fafd3ec9
Name Last commit Last update
bl1 linker_script: move .data section to bl_common.ld.h
bl2 TF-A: Add support for Measured Boot driver in BL1 and BL2
bl2u linker_script: move .data section to bl_common.ld.h
bl31 runtime_exceptions: Update AT speculative workaround
bl32 linker_script: move .rela.dyn section to bl_common.ld.h
common Add wrapper for AT instruction
docs Merge "doc: Minor formatting improvement in the coding guidelines document" into integration
drivers plat/allwinner: Only enable DRIVEVBUS if really needed
fdts Merge "SPM: build OP-TEE as an S-EL1 Secure Partition" into integration
include SPMC: manifest changes to support multicore boot
lib Merge "Revert "libc/memset: Implement function in assembler"" into integration
make_helpers plat/arm: Use common build flag for using generic sp804 driver
plat Merge "Revert "libc/memset: Implement function in assembler"" into integration
services SPMC: embed secondary core ep info into to SPMC context
tools tools: Get the tool's binary name from the main makefile
.checkpatch.conf Re-apply GIT_COMMIT_ID check for checkpatch
.editorconfig doc: Final, pre-release fixes and updates
.gitignore Ignore the ctags file
.gitreview Specify integration as the default branch for git-review
Makefile tools: Get the tool's binary name from the main makefile
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

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.