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.
