55b41af673
Update trusted-firmware-a to lts-v2.10.12 Changes between 7e63213601425c7a6d83e47dc936b264deb9df2b and 408ba4ddfe9a8d55e3e2488bea89c39adef07981 408ba4ddfe9a docs(changelog): changelog for lts-v2.10.12 release 7bdf51628eab Merge "docs(maintainers): update LTS maintainers" into lts-v2.10 8355ef7728ec docs(maintainers): update LTS maintainers faceedf4e5c2 Merge changes from topic "for-lts-v2.10.12" into lts-v2.10 9007a3344e12 Merge changes from topic "gr/lts-doc-2.10" into lts-v2.10 924c7f42ce4a chore(deps): bump cross-spawn 7c8c034e5fed chore(deps): bump jinja2 in the pip group across 1 directory 3d85a19f2f54 docs: updates to LTS 13657a3f3f2a docs: add inital lts doc a4c57c122407 Merge changes from topic "lts-v2.10.12" into lts-v2.10 564922601397 feat(mbedtls): mbedtls config update for v3.6.2 44161dcb10ab docs(prerequisites): update mbedtls to version 3.6.2 0ac65e7aa5ec refactor(mbedtls): rename default mbedtls confs 8b2c885739dd fix(arm): add extra hash config to validate ROTPK 832b92b7f615 docs(changelog): changelog for lts-v2.10.11 release a3fc7c18c461 Merge changes from topic "for-lts-2.10.11" into lts-v2.10 196984e65da0 fix(cpus): workaround for Cortex-X4 erratum 2923985 0eed05ee70aa chore(cpus): optimise runtime errata applications 34e6d7cb8ce1 Merge changes from topic "sm/fix_erratum" into lts-v2.10 ad9dfdc5800c fix(cpus): workaround for CVE-2024-5660 for Cortex-X2 5673d345aaa3 fix(cpus): workaround for CVE-2024-5660 for Cortex-A77 4fd2a6702dd1 fix(cpus): workaround for CVE-2024-5660 for Neoverse-V1 a02a863d3156 fix(cpus): workaround for CVE-2024-5660 for Cortex-A78_AE 87250d2bb1ea fix(cpus): workaround for CVE-2024-5660 for Cortex-A78C 30c57c58abe3 fix(cpus): workaround for CVE-2024-5660 for Cortex-A78 c7d3c9eb2d81 fix(cpus): workaround for CVE-2024-5660 for Cortex-X1 282e63544d26 fix(cpus): workaround for CVE-2024-5660 for Neoverse-N2 f7ae819f03ae fix(cpus): workaround for CVE-2024-5660 for Cortex-A710 3efc9e13011d fix(cpus): workaround for CVE-2024-5660 for Neoverse-V2 17e17ed3f1e6 fix(cpus): workaround for CVE-2024-5660 for Cortex-X3 a6375e1feb42 fix(cpus): workaround for CVE-2024-5660 for Neoverse-V3 e42abf298321 fix(cpus): workaround for CVE-2024-5660 for Cortex-X4 698e68fe1fe9 fix(cpus): workaround for CVE-2024-5660 for Cortex-X925 b229b47bd86c chore: rename Blackhawk to Cortex-X925 96498991d1ce chore: rename Chaberton to Cortex-A725 b28aa38e28cf docs(changelog): changelog for lts-v2.10.10 release 8e74814ce52f Merge changes from topic "for-lts-v2.10.10" into lts-v2.10 c9f3fb5822dc build(deps): bump setuptools in the pip group across 1 directory 395ef3534cf1 chore(deps): bump micromatch 6c6e986bffb3 build(npm): update Node.js and all packages c5d2a030a35f build(deps): bump braces ebf6430a01c5 build(deps): bump idna from 3.4 to 3.7 93ad43e79ef7 build(deps): bump jinja2 from 3.1.2 to 3.1.4 f8a06a0f82ce build(deps): bump urllib3 from 2.0.2 to 2.2.2 3ea256c36a4b build(deps): bump pip from 23.1.2 to 23.3 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