aboutsummaryrefslogtreecommitdiffstats
path: root/include/trusted-firmware-a.mk
Commit message (Collapse)AuthorAgeFilesLines
* trusted-firmware-a: fix project name spellingDaniel Golle2021-02-131-1/+1
| | | | | | | The version string generated for ARM Trusted-Firmware-A was stated as "OpenWRT". Fix that by changing it to the exact spelling "OpenWrt" Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* trusted-firmware-a.mk: add PKG_CPE_IDDaniel Golle2021-02-041-0/+1
| | | | | | | Vulnerabilities of Trusted Firmware A are tracked as cpe:/a:arm:arm_trusted_firmware Signed-off-by: Daniel Golle <daniel@makrotopia.org>
* trusted-firmware-a.mk: pass package version as version identifierAndre Heider2021-01-301-0/+1
| | | | | | | Upon boot it now prints: NOTICE: BL1: v2.4(release):OpenWRT v2.4-1 (espressobin-v3-v5-1gb-2cs) (Marvell-devel-18.12.0) Signed-off-by: Andre Heider <a.heider@gmail.com>
* build: Extract trusted-firmware-a.mkHauke Mehrtens2020-12-021-0/+93
The include/trusted-firmware-a.mk file is based on the include/u-boot.mk file and should be used to build a Trusted Firmware-A (TFA) which was previously named Arm trusted firmware. This is useful for targets where the TFA is board specific like for Marvell SoCs and probably also NXP Layerscape SoCs. This also makes use of this abstraction in the arm-trusted-firmware-mvebu package to build board specific ATF binaries. The ATF binaries will be automatically activated and build when the board is selected in the normal build or all boards are selected. This should also activate the build when build bot creates images. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>