Jon Mason
f78c6c0e4f
Update to the lts-v2.12.1 tag. Changes include a number of CVE fixes and mbedtls minor version bump: 8cf9edba5cc3 docs(changelog): changelog for lts-v2.12.1 release f5d048108bf3 Merge changes from topic "for-lts-v2.12.1" into lts-v2.12 56472775f96d docs(maintainers): update LTS maintainers baab55315c7f docs: updates to LTS f00f71efc410 docs: add inital lts doc 1a8ee82c6d77 Merge changes from topic "for-lts-v2.12.1" into lts-v2.12 b19ce90a908c fix(rd1ae): fix rd1-ae device tree 34f10e7d9fc7 feat(rd1ae): add Generic Timer in device tree 551dc4c09f57 docs(rd1ae): update documentation to include BL32 8e4240779867 feat(rd1ae): add support for OP-TEE SPMC 8e4bb69c747e feat(mbedtls): mbedtls config update for v3.6.2 a46d6a1320d7 docs(prerequisites): update mbedtls to version 3.6.2 2ffe181a3982 refactor(mbedtls): rename default mbedtls confs 3809359e2124 fix(cpus): workaround for Neoverse-V3 erratum 3701767 4a9ff092c9b4 fix(cpus): workaround for Neoverse-N3 erratum 3699563 7e41b706e97c fix(cpus): workaround for Neoverse-N2 erratum 3701773 15300ac30c55 fix(cpus): workaround for Cortex-X925 erratum 3701747 6e0efc7fe739 fix(cpus): workaround for Cortex-X4 erratum 3701758 8299c1274617 fix(cpus): workaround for Cortex-X3 erratum 3701769 fa6c9874485b fix(cpus): workaround for Cortex-X2 erratum 3701772 4e78288fd2bc fix(cpus): workaround for Cortex-A725 erratum 3699564 ae6edfd5b543 fix(cpus): workaround for Cortex-A720-AE erratum 3699562 24526273fc50 fix(cpus): workaround for Cortex-A720 erratum 3699561 a7b322706435 fix(cpus): workaround for Cortex-A715 erratum 3699560 d4826882210b fix(cpus): workaround for Cortex-A710 erratum 3701772 9d6143ec8ffb fix(cpus): workaround for accessing ICH_VMCR_EL2 7e4bf042a0dd chore(cpus): fix incorrect header macro 9427c061eb8d fix(security): apply SMCCC_ARCH_WORKAROUND_4 to affected cpus bea64fd5272d fix(security): add support in cpu_ops for CVE-2024-7881 16b87247ed03 fix(security): add CVE-2024-7881 mitigation to Cortex-X3 427c33bc0c0b fix(security): add CVE-2024-7881 mitigation to Neoverse-V3 192a152448ae fix(security): add CVE-2024-7881 mitigation to Neoverse-V2 3e4d94c43b64 fix(security): add CVE-2024-7881 mitigation to Cortex-X925 41a52efd6f38 fix(security): add CVE-2024-7881 mitigation to Cortex-X4 2f09b9f3c2af fix(security): enable WORKAROUND_CVE_2024_7881 build option 70a7d3f2d030 fix(cpus): workaround for CVE-2024-5660 for Cortex-X925 41b64fe36f42 fix(cpus): workaround for CVE-2024-5660 for Cortex-X2 0b2d22097c96 fix(cpus): workaround for CVE-2024-5660 for Cortex-A77 193370e1c6a2 fix(cpus): workaround for CVE-2024-5660 for Neoverse-V1 d52c52a5fa8c fix(cpus): workaround for CVE-2024-5660 for Cortex-A78_AE 3bd6531a55a4 fix(cpus): workaround for CVE-2024-5660 for Cortex-A78C eda09acd1b22 fix(cpus): workaround for CVE-2024-5660 for Cortex-A78 b9766da96365 fix(cpus): workaround for CVE-2024-5660 for Cortex-X1 6324220805b1 fix(cpus): workaround for CVE-2024-5660 for Neoverse-N2 6041f0723994 fix(cpus): workaround for CVE-2024-5660 for Cortex-A710 b23f5da614e6 fix(cpus): workaround for CVE-2024-5660 for Neoverse-V2 ef378713fa4b fix(cpus): workaround for CVE-2024-5660 for Cortex-X3 2898088f8ba6 fix(cpus): workaround for CVE-2024-5660 for Neoverse-V3 b8e111c72619 fix(cpus): workaround for CVE-2024-5660 for Cortex-X4 a6f6396313ea fix(cpus): workaround for Cortex-X4 erratum 2923985 d1c3a5d8b9d8 fix(build): do not force PLAT in plat_helpers.mk ea1b816b1763 chore(deps): update pytest for cot-dt2c 65762d7b4cfc chore(deps): bump jinja2 87f3125a0e45 chore(deps): bump jinja2 in the pip group across 1 directory b4530565c030 chore(deps): bump the pip group across 2 directories with 1 update 11e5f92d3d43 build(deps): bump setuptools in the pip group across 1 directory 850389f4acfe chore(deps): bump micromatch 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