b31af92555
Update trusted-firmware-m to the latest LTS (TF-Mv2.1.1) Changes between 0c4c99ba33b3e66deea070e149279278dc7647f4 and 02bf279913439a07082dd581df033f370a8fbb92 02bf27991343 docs: Release notes for v2.1.1 7264a32e84a0 docs: rp2350: Minor docs & script improvements 4bad159af017 Docs: Release dates update a5e02ec0c6a2 Align .gitignore contents to main branch 8fe944a652f5 Platform: RP2350: Fix NV counters in ITS 66bc1fa8eed9 Build: Fix patch formatting for 0001-iar-Add-missing-v8.1m-check.patch 895d44a4eb52 Platform: RP2350: Add NV counters to ITS e81b741aa6cc tf-m-tests: Step version for rp2350 psa-arch-tests 2be65a027c86 Platform: rp2350: Add rwx linker flag conditionally for GNUARM a85425417696 Platform: RP2350: Add RP2350 porting 9ed2e7c7f52b Platform/TFM/ITS/Config: Commits required for new platform porting f12db7c872d5 cc3xx/low-level/pka: SRAM size depends on CC3XX version c7e0192fab6f cc3xx/low-level/hash: wait for hash engine to be idle 42a4041bdff4 Crypto: Update to Mbed TLS 3.6.2 471c127e7755 Crypto: Add option to enforce ABI compatibility 7da71fd05445 tfm_spe_mailbox: Fix NULL pointer checks 974bc101e0b2 cc3xx/low-level/pka: wait for sw reset to be done before proceeding 89b9c4889c60 Crypto: Enforce MBEDTLS_PSA_ASSUME_EXCLUSIVE_BUFFERS on Mbed TLS config 62b1300557c5 Crypto: Additional checks for writes to avoid out-of-bound access a2cead6a9ef4 tfm_spe_mailbox: Use local vars for local_copy_vects 15afe61d1194 TFMV-8: Fix unchecked user-supplied pointer via mailbox message 22e8e89c8f56 tfm_spe_mailbox: Do not write-back on input vectors checks failure 12a4c5342965 tfm_spe_mailbox: Validate vectors from NSPE 75bbe3fc0240 CC3XX: Relax assert condition in aead_crypt for input 0db7ebf32ba3 Crypto: Protect writes to avoid out-of-bound access 2ecea430fbb4 Crypto: Prevent the scratch allocator from overflowing fbcdc69b794d SPM: mailbox_agent_api: Free connection if params association fails 2a59580b5809 Crypto: Update to Mbed TLS 3.6.1 6a54ec89f22f Platform: STM32: script all_stm_platfrom 66596b4dae57 Platform: corstone1000: Fix isolation L2 memory protection 7045675209ca stm : fix error on b_u585i_iot02a with TF-Mv2.1.0 Signed-off-by: Jon Mason <jon.mason@arm.com>
Introduction
This repository contains the Arm layers for OpenEmbedded.
-
meta-arm
This layer contains general recipes for the Arm architecture, such as firmware, FVPs, and Arm-specific integration.
-
meta-arm-bsp
This layer contains machines for Arm reference platforms, for example FVP Base, Corstone1000, and Juno.
-
meta-arm-toolchain
This layer contains recipes for Arm's binary toolchains (GCC and Clang for -A and -M), and a recipe to build Arm's GCC.
Other Directories
-
ci
This directory contains gitlab continuous integration configuration files (KAS yaml files) as well as scripts needed for this.
-
documentation
This directory contains information on the files in this repository, building, and other relevant documents.
-
kas
This directory contains KAS yaml files to describe builds for systems not used in CI.
-
scripts
This directory contains scripts used in running the CI tests.
Mailing List
To interact with the meta-arm developer community, please email the meta-arm mailing list at meta-arm@lists.yoctoproject.org. Currently, it is configured to only allow emails to members from those subscribed. To subscribe to the meta-arm mailing list, please go to https://lists.yoctoproject.org/g/meta-arm
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
All contributions are under the MIT License.
For a quick start guide on how to build and use meta-arm, go to quick-start.md.
For information on the continuous integration done on meta-arm and how to use it, go to continuous-integration-and-kas.md.
Backporting
Backporting patches to older releases may be done upon request, but only after a version of the patch has been accepted into the master branch. This is done by adding the branch name to email subject line. This should be between the square brackets (e.g., "[" and "]"), and before or after the "PATCH". For example,
[nanbield PATCH] arm/linux-yocto: backport patch to fix 6.5.13 networking issues
Automatic backporting will be done to all branches if the "Fixes: " wording is added to the patch commit message. This is similar to how the Linux kernel community does their LTS kernel backporting. For more information see the "Fixes" portion of https://www.kernel.org/doc/html/latest/process/submitting-patches.html#submittingpatches
Releases and Release Schedule
We follow the Yocto Project release methodology, schedule, and stable/LTS support timelines. For more information on these, please reference:
- https://docs.yoctoproject.org/ref-manual/release-process.html
- https://wiki.yoctoproject.org/wiki/Releases
- https://wiki.yoctoproject.org/wiki/Stable_Release_and_LTS
For more in-depth information on the meta-arm release and branch methodology, go to </documentation/releases.md>.
Reporting bugs
E-mail meta-arm@lists.yoctoproject.org with the error encountered and the steps to reproduce the issue.
Security and Reporting Security Issues
For information on the security of meta-arm and how to report issues, please consult SECURITY.md.
Maintainer(s)
- Jon Mason jon.mason@arm.com
- Ross Burton ross.burton@arm.com