Khasim Mohammed
3fc917ac8f
Device tree blobs (DTBs) generated as part of TFA were installed separately in the platform specific TFA recipes, its redundant as each platform was executing similar installation steps. The patch avoids skipping dtb installation and adds support to check for DTB entries in TFA_INSTALL_TARGET and install the same to respective deploy folder. Change-Id: I0f8f5c39dc4b4931d202696990fa915ea7ed60eb Issue-Id: PLATFORMS-3971 Signed-off-by: Khasim Syed Mohammed <khasim.mohammed@arm.com> Signed-off-by: Jon Mason <jon.mason@arm.com>
Introduction
This repository contains Arm layers for OpenEmbedded
meta-arm: This layer provides support for general recipes for the Arm architecture. Anything that's not needed explicitly for BSPs, the IOTA distribution, or destined to be upstreamed belongs here.
meta-arm-bsp: This layer provides support for Arm reference platforms
meta-arm-iota: This layer provides support for Arm's IOTA Linux Distribution
meta-arm-toolchain: This layer provides support for Arm's GNU-A toolset releases
meta-arm-autonomy: This layer provides a reference stack for autonomous systems.
Contributing
Currently, we only accept patches from the meta-arm mailing list. For general information on how to submit a patch, please read https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded
E-mail meta-arm@lists.yoctoproject.org with patches created using this process. You can configure git-send-email to automatically use this address for the meta-arm repository with the following git command:
$ git config --local --add sendemail.to meta-arm@lists.yoctoproject.org
Commits and patches added should follow the OpenEmbedded patch guidelines:
https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
The component being changed in the shortlog should be prefixed with the layer name (without the meta- prefix), for example:
arm-bsp/trusted-firmware-a: decrease frobbing level
arm-toolchain/gcc: enable foobar v2
Reporting bugs
E-mail meta-arm@lists.yoctoproject.org with the error encountered and the steps to reproduce the issue.
Maintainer(s)
- Jon Mason jon.mason@arm.com
- Ross Burton ross.burton@arm.com