3 Commits

Author	SHA1	Message	Date
Daniel Golle	104d60fe94	trusted-firmware-a.mk: add PKG_CPE_ID ... Vulnerabilities of Trusted Firmware A are tracked as cpe:/a:arm:arm_trusted_firmware Signed-off-by: Daniel Golle <daniel@makrotopia.org>	2021-02-04 01:05:12 +00:00
Andre Heider	4c6c1c6dd0	trusted-firmware-a.mk: pass package version as version identifier ... 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>	2021-01-30 14:46:32 +01:00
Hauke Mehrtens	d346beb08c	build: Extract trusted-firmware-a.mk ... 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>	2020-12-02 23:46:01 +01:00