aboutsummaryrefslogtreecommitdiffstats
path: root/package/boot/arm-trusted-firmware-mvebu/patches
Commit message (Collapse)AuthorAgeFilesLines
* arm-trusted-firmware-mvebu: Use host flags for cryptest compilationHauke Mehrtens2022-12-311-0/+13
| | | | | | | | | Without these changes it used the system LDFLAGS for the compilation of the cryptopp library. This does not always work when we add "-no-warn-rwx-segments" which is done to support binutils 2.39 inside of OpenWrt. Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
* arm-trusted-firmware-mvebu: update to v2.7Andre Heider2022-07-316-432/+21
| | | | | | | Remove the backported patches and add another to allow building with the OpenWrt build system. Signed-off-by: Andre Heider <a.heider@gmail.com>
* arm-trusted-firmware-mvebu: add cryptoppJosef Schlehofer2021-11-271-20/+0
| | | | | | | | | | | | | | | Based on the Build Instructions for Trusted-Firmware-A [1], there is a required cryptopp [2]. In the past, it used 'tbb_linux' image tool binary, which seems to be buggy, deprecated and removed from A3700-utils-marvell and it should not be used anymore. That's why I removed 001-imagetool.patch, which is no longer necessary. [1] https://trustedfirmware-a.readthedocs.io/en/v2.5/plat/marvell/armada/build.html [2] https://cryptopp.com/ Signed-off-by: Josef Schlehofer <pepe.schlehofer@gmail.com>
* arm-trusted-firmware-mvebu: update to v2.5Andre Heider2021-07-255-0/+432
| | | | | | | | | | | Revert to using the checked in `tbb_linux` image tool binary since building it drags in the rather big Crypto++ project. Cherry-pick the post-release UART fixes. Switch to AUTORELEASE while at it. Signed-off-by: Andre Heider <a.heider@gmail.com>
* arm-trusted-firmware-mvebu: update to v2.4Andre Heider2021-01-301-2/+2
| | | | Signed-off-by: Andre Heider <a.heider@gmail.com>
* arm-trusted-firmware-mvebu: update to v2.3Andre Heider2020-09-181-0/+20
Switch to release tarballs and add missing license information while here. Signed-off-by: Andre Heider <a.heider@gmail.com>