Specify signed-ness of constants
Jimmy Brisson authored
We relyed on the default signed-ness of constants, which is usually
signed. This can create MISRA violations, such as:

     bl1/bl1_main.c:257:[MISRA C-2012 10.8 (required)] Cast of composite
     expression off essential type signed to essential type unsigned

These constants were only used as unsigned, so this patch makes them
explicitly unsigned.

Change-Id: I5f1310c881e936077035fbb1d5ffb449b45de3ad
Signed-off-by: default avatarJimmy Brisson <jimmy.brisson@arm.com>
e1d5be56
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 linker_script: move .rela.dyn section to bl_common.ld.h
bl32 linker_script: move .rela.dyn section to bl_common.ld.h
common plat/fvp: Support for extracting UART serial node info from DT
docs Merge "TF-A AMU extension: fix detection of group 1 counters." into integration
drivers tbbr/dualroot: rename SP package certificate file
fdts Merge "SPM: build OP-TEE as an S-EL1 Secure Partition" into integration
include Specify signed-ness of constants
lib Merge "lib: cpus: denver: mark exception vectors as private" into integration
make_helpers Makefile, doc: Make OPENSSL_DIR variable as build option for tools
plat Prevent colliding identifiers
services SMCCC: Introduce function to check SMCCC function availability
tools Use abspath to dereference $BUILD_BASE
.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 Merge "Use abspath to dereference $BUILD_BASE" into integration
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.