summaryrefslogtreecommitdiffstats
path: root/recipes-bsp/imx-mkimage/imx-boot_1.0.bb
diff options
context:
space:
mode:
authorAndrey Zhizhikin <andrey.z@gmail.com>2022-06-13 09:05:11 +0000
committerOtavio Salvador <otavio@ossystems.com.br>2022-06-16 16:53:46 -0300
commit9c62ef822225c253a53bfce291f8f19f96cae658 (patch)
treebd5a7436676e10563196dd246011f3916a44be3f /recipes-bsp/imx-mkimage/imx-boot_1.0.bb
parentbdead7c58cf7357f6b12fb25f4f34e06f4370702 (diff)
downloadmeta-freescale-9c62ef822225c253a53bfce291f8f19f96cae658.tar.gz
layer-wide: define configurable default TF-A provider
TF-A package can have several providers: upstream TF-A implementation, or NXP downstream fork. Functionality to switch this provider, and to select which package shall be included into the target image is missing in the layer however, defaulting the usage of the layer to NXP downstream fork only. Introduce the Default TF-A Provider define, make it overridable, and default it to NXP downstream fork. This allows user to re-define the package name later shall they choose to integrate upstream TF-A package instead. Current upstream TF-A version (v2.7) does not support HAB feature of i.MX8M family, see [1]. If the upstream TF-A version is chosen, then HAB will not be available for all SoCs that are opting-in. This is indicated in the comment where default TF-A provider variable is set. This might change with future TF-A release, so later it can be revised and statement in include file can be potentially removed. Signed-off-by: Andrey Zhizhikin <andrey.z@gmail.com> Link: [1]: https://lists.trustedfirmware.org/archives/list/tf-a@lists.trustedfirmware.org/message/5UYYI4CNLQ5OWWHU466JBK6I5QIQ2VRS/ (cherry picked from commit b61c4907b1926061cbf627ee1fd5dd8eb8e53d59)
Diffstat (limited to 'recipes-bsp/imx-mkimage/imx-boot_1.0.bb')
0 files changed, 0 insertions, 0 deletions