External email: Use caution opening links or attachments
Hello,
As announced in the last Tech forum, the code freeze date for the LTS branch is Feb 3, 2023. We have now locked the branch and won’t be accepting any more commits.
The list of the commits that will be merged into the LTS branch can be found at ⚡ LTS Tracking for v2.8.x (trustedfirmware.org)<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdeveloper…>. If there are commits that we missed or that need to be in the LTS branch, please reach out to us.
We will post more updates shortly.
Thanks.
Hello,
As announced in the last Tech forum, the code freeze date for the LTS branch is Feb 3, 2023. We have started shortlisting the patches for the lts-v2.8 branch.
These are the commits that will be merged into the LTS branch. More details can be found at ⚡ LTS Tracking for v2.8.x (trustedfirmware.org)<https://developer.trustedfirmware.org/w/tf_a/tf-a_lts_meeting_minutes/track…>
1. c7e698cfd fix(cpus): workaround for Cortex-X3 erratum 2615812
2. c45791b2f fix(layerscape): fix errata a008850
3. fa0105693 fix(nxp-ddr): use CDDWW for write to read delay
4. 00bb8c37e fix(nxp-ddr): apply Max CDD values for warm boot
5. 07d8e34fd fix(nxp-drivers): fix tzc380 memory regions config
6. c0c157a68 fix(ls1046a): 4 keys secureboot failure resolved
7. 50aa0ea7a fix(lx2): init global data before using it
8. 4daeaf341 fix(sptool): add dependency to SP image
9. 5fb6946ad fix(console): fix crash on spin_unlock with cache disabled
10. ff1d2ef38 fix(el3_runtime): restore SPSR/ELR/SCR after esb
11. c42402cdf fix(intel): fix fcs_client crashed when increased param size
12. 0ca1d8fba fix(layerscape): unlock write access SMMU_CBn_ACTLR
13. b87b02cf1 fix(cpus): workaround for Cortex-A710 erratum 2768515
14. 1cfde8222 fix(cpus): workaround for Cortex-X2 erratum 2768515
15. 377846b65 fix(st): include utils.h to solve compilation error
16. 1cbe42a51 fix(el3_runtime): allow SErrors when executing in EL3
17. 1ee7c8232 fix(cpus): workaround for Neoverse N2 erratum 2743089
18. b10afcce5 fix(cpus): workaround for Cortex-A78 erratum 2772019
19. 31747f057 fix(cpus): workaround for Neoverse V1 erratum 2743093
20. fd37982a1 fix(auth): forbid junk after extensions
21. 72460f50e fix(auth): require at least one extension to be present
22. 06c01b085 fix(libc): properly define SCHAR_MIN
23. 89d85ad0a fix(cpus): workaround for Cortex-A710 erratum 2282622
24. abb8f936f fix(auth): avoid out-of-bounds read in auth_nvctr()
25. f5c51855d fix(auth): properly validate X.509 extensions
26. f9c6301d7 fix(cpus): workaround for Cortex-X2 erratum 2282622
27. 60719e4e0 fix(plat/css): fix invalid redistributor poweroff
28. 00230e37e fix(cpus): workaround for Cortex-A78C erratum 2772121
29. aea4ccf8d fix(cpus): workaround for Cortex-A510 erratum 2684597
If there are commits that we missed or that need to be in the LTS branch, please reach out to us.
Thanks.
Hello ST maintainers,
Hope you are doing well.
The merge window for the next LTS release is now open. We are collecting changes for the release and need your input.
Can you please help us decide if the following patches should be part of the LTS release?
1. 377846b65 fix(st): include utils.h to solve compilation error
2. d1d8a9bad fix(st): make metadata_block_spec static
3. 6e55f9e2c fix(stm32mp1): add missing platform.h include
4. 70a422ba8 fix(st-crypto): set get_plain_pk_from_asn1() static
Thanks.
Hello NXP maintainers,
Hope you are doing well.
The merge window for the next LTS release is now open. We are collecting changes for the release and need your input.
Can you please help us decide if the following patches should be part of the LTS release?
1. e49229911 fix(nxp-crypto): fix coverity issue
2. c0c157a68 fix(ls1046a): 4 keys secureboot failure resolved
3. 50aa0ea7a fix(lx2): init global data before using it
4. 87612eaef fix(nxp-ddr): fix underrun coverity issue
Thanks.
Hi,
Happy new year!
For NVIDIA Tegra platforms, we need the capability to query the BL31 version (e.g. 2.7, 2.8, 2.8.x) from the NWd at runtime. I could not find an FID that returns this value.
I propose we introduce a new runtime service in bl31 that returns the version_string to the NWd to support this requirement.
Thoughts?
-Varun
Hello Intel maintainers,
Hope you are doing well.
The merge window for the next LTS release is now open. We are collecting changes for the release and need your input.
Can you please help us decide if the following patch should be part of the LTS release?
1. b34a48c1c fix(intel): missing NCORE CCU snoop filter fix in BL2
If the patch satisfies one of the following, then it would be a good candidate for release.
1. Does this patch fix a security vulnerability?
2. Does this patch implement a fix for a platform erratum?
3. Does this patch fix a critical issue for the platform?
Thanks.
All,
Here is a quick update on the LTS release planning and progress before we break for the holidays.
The following branches are created which are derived from TF-A v2.8 release for the purpose of the LTS release.
TF-A
trusted-firmware-a.git - Trusted Firmware for A profile Arm CPUs<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.trust…>
TFTF
tf-a-tests.git - Trusted Firmware-A Tests<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.trust…>
tf-a-ci-scripts
tf-a-ci-scripts.git - Trusted Firmware A (TF-A) CI scripts<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.trust…>
tf-a-job-configs
tf-a-job-configs.git - Trusted Firmware A (TF-A) Jenkins job configs<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.trust…>
Following are planned for January - February 2023.
1. A Tech Forum explaining the LTS process (Jan 2023)
2. Creation of an LTS RC tag ( Early Feb 2023)
3. First TF-A LTS release (Mid Feb 2023)
For more info on TF-A LTS, here is the link to the announcement on tf.org. First LTS Release of Trusted Firmware - A (TF-A) - Trusted Firmware<https://www.trustedfirmware.org/news/LTS-Release/>
Thanks & best regards,
Bipin Ravi
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
