January 2026 - TF-A - lists.trustedfirmware.org

Trusted Firmware-A LTS v2.12.9 Release Announcement

by svc_openci_enginfra＠arm.com

Hello, Trusted Firmware-A LTS version 2.12.9 is now available. This release contains the following patches: 78fb9b745 fix(security): fix spectre bhb loop count for Cortex-A720 [1] 6d19bed6a fix(security): fix Cortex-A715 CVE-2022-23960 [2] dd0d59764 fix(security): fix Cortex-X3 CVE-2022-23960 [3] d69858d6e fix(security): fix Neoverse V2 CVE-2022-23960 [4] f1b4da3e6 fix(security): remove CVE_2022_23960 Cortex-X4 [5] 9afe25a13 fix(security): remove CVE_2022_23960 Neoverse V3 [6] b75f2db65 fix(security): remove CVE_2022_23960 Cortex-A720 [7] 6c535b5ae feat(cpufeat): do feature detection on secondary cores too [8] b173b7948 fix(cpufeat): do feature detection before feature enablement [9] 0df7d4ca0 fix(security): add clrbhb support [10] ed331c19c fix(cpus): workaround for Cortex-A715 erratum 2409570 [11] 214d51629 fix(cpus): workaround for Cortex-A715 erratum 2376701 [12] 3f73a85fb fix(cpus): workaround for Cortex-A715 erratum 3711916 [13] 71d033c7b fix(cpus): workaround for Cortex-A76AE erratum 1931427 [14] bfe756d61 fix(cpus): workaround for Cortex-A76AE erratum 1931435 [15] d24cf8d8f fix(cpus): workaround for Cortex-A76AE erratum 1969401 [16] 8b11b602c fix(cpus): workaround for Cortex-A76AE erratum 2371140 [17] f5daa76a2 fix(build): set ERRATA_SPECULATIVE_AT after platform.mk [18] ef2975fbe fix(cpus): workaround for Cortex-A65 erratum 1179935 [19] 655417b85 fix(cpus): workaround for Cortex-A65 erratum 1227419 [20] bf539177b fix(cpus): workaround for Cortex-A65 erratum 1541130 [21] aad5e748c fix(cpus): workaround for Cortex-A725 erratum 2874943 [22] 58130aca2 fix(cpus): workaround for Cortex-A725 erratum 2936490 [23] d3771e5eb fix(cpus): workaround for Cortex-A725 erratum 3711914 [24] a5dc91815 fix(cpus): workaround for Cortex-A725 erratum 3456106 [25] f557bb983 docs(security): add CVE-2024-5660 and CVE-2024-7881 reference links [26] 98efb2cdd fix(security): update Cortex-X4 fix version for CVE-2024-7881 [27] 53b539727 fix(security): update Neoverse-V3/V3AE fix version for CVE-2024-7881 [28] cd24fc78d fix(security): update Cortex-X3 fix version for CVE-2024-7881 [29] 03b289bd5 fix(security): update Neoverse-V2 fix version for CVE-2024-7881 [30] d2e5cb077 docs(security): update CVE-2024-7881 affected CPU revisions [31] 5aa4bb35a fix(cpus): register ARCH_WORKAROUND_3 for Neoverse V2 [32] c462d3e26 fix(cpus): workaround for Cortex-A710 erratum 3324338 [33] 17f11f645 fix(cpus): workaround for Cortex-X2 erratum 3324338 [34] c5af478c0 fix(cpus): workaround for Cortex-A715 erratum 3456084 [35] 58a6ddd23 fix(cpus): workaround for Cortex-A720 erratum 3456091 [36] 5bbe15b28 fix(fvp): avoid stack usage in check_cpupwrctrl_el1_is_available() [37] [1] https://review.trustedfirmware.org/q/Ib6862dbed55e5ffcd0fcd58b45a88cf925c54… [2] https://review.trustedfirmware.org/q/Ib6b704733e474824772cb27bd048b1e179d90… [3] https://review.trustedfirmware.org/q/I3d46fa70c80129ca0085d8245ee013f11a884… [4] https://review.trustedfirmware.org/q/I859012281fc67243f050d27e364f27434389c… [5] https://review.trustedfirmware.org/q/I23f5fa748377a920340b3c5a6584ccfadeea9… [6] https://review.trustedfirmware.org/q/I13b27c04c3da5ec80fa79422b4ef4fee64738… [7] https://review.trustedfirmware.org/q/I3c68b5f5d85ede37a6a039369de8ed2aa9205… [8] https://review.trustedfirmware.org/q/Iee4955714685be9ae6a017af4a6c284e835ff… [9] https://review.trustedfirmware.org/q/I47f05a9f01321e011623083afb638552311ed… [10] https://review.trustedfirmware.org/q/Ie6e56e96378503456a1617d5e5d51bc64c2e0… [11] https://review.trustedfirmware.org/q/Id9429831525b842779d7b7e60f103c93be4ac… [12] https://review.trustedfirmware.org/q/Idcd2a07d269d55534dc5faa59c454d37426f2… [13] https://review.trustedfirmware.org/q/Iad149a2c02a804b3f4f0f2f5b89e866675cb4… [14] https://review.trustedfirmware.org/q/I31566838f894372e5627abda8b0bea1505f11… [15] https://review.trustedfirmware.org/q/I1baba8752f5f2e2ab5c873030e1f00cbb8cf1… [16] https://review.trustedfirmware.org/q/I893452450d430833e6c5a8e33a1e37b708218… [17] https://review.trustedfirmware.org/q/Id65846bebde1a0911ba11956202d0d255d3c8… [18] https://review.trustedfirmware.org/q/I221dab39c417531c5a148886d3e29709ba8b5… [19] https://review.trustedfirmware.org/q/Ie59a4897f849269a590d8fa2d25cceab5f2cb… [20] https://review.trustedfirmware.org/q/I42371e7d53fce3a7e085bf0b348f080fa323f… [21] https://review.trustedfirmware.org/q/I72498f60f8449193ed4b5b2a9e7a08530e786… [22] https://review.trustedfirmware.org/q/I686bbde8756d52afee92097ec05b97138b550… [23] https://review.trustedfirmware.org/q/I9833f8831ba3735a94763791a65be11b95c00… [24] https://review.trustedfirmware.org/q/If3b9d3a0f495b3a172d3e6e5ca7afa8c30aeb… [25] https://review.trustedfirmware.org/q/I10d1e8cb4da19ba4101a5617245ff75866707… [26] https://review.trustedfirmware.org/q/Ia3c003d5c359f101f230fbd54845f61117456… [27] https://review.trustedfirmware.org/q/Iae84f26fdce96a61fdc942b7595ccf8b9c778… [28] https://review.trustedfirmware.org/q/If3e2989a4b5a5c68dc12e23978b226c73f21b… [29] https://review.trustedfirmware.org/q/Ia1ff75602a0dfa758a223549d92ea87543fa4… [30] https://review.trustedfirmware.org/q/I1ae196fa8ce4579524faba4916f631e7c4db3… [31] https://review.trustedfirmware.org/q/Iad109561a144169fd3805c179a4f8e3bfdd59… [32] https://review.trustedfirmware.org/q/I8c08c26e0b7c268772d75d36d759564a7d67c… [33] https://review.trustedfirmware.org/q/I9325f3715f4fa17bfb7ded9d5c69c59645f65… [34] https://review.trustedfirmware.org/q/Ibbe55a55bd6cf5e159dab92a78ecb55c5a4d7… [35] https://review.trustedfirmware.org/q/Ie3f2b46051539cdebc151c46f80045a7156e0… [36] https://review.trustedfirmware.org/q/Ia22a0d6bb98d1a0edb11d2469beab22c7f7ab… [37] https://review.trustedfirmware.org/q/I920e32c34bddf86a1dbf05b7115026413483b… Alternatively, Change Log is available in the documentation section: https://trustedfirmware-a.readthedocs.io/en/lts-v2.12.9/change-log.html Thanks, TF-A LTS team

6 days, 1 hour

1
0
0 0

TF-A Tech Forum Jan 22nd 10.00am UK -Part II Scaling Hafnium for advanced mobile OS architectures

by Olivier Deprez

(re-sending as previous invitation got lost) Hi, As follow up to the last session on Nov 13th 2025 [1], a new TF-A Tech Forum session with the topic 'Scaling Hafnium for advanced mobile OS architectures' will be held on Jan 22nd 2026 10.00am. Regards, Olivier. [1] https://www.trustedfirmware.org/meetings/tf-a-technical-forum/ Scaling Hafnium for advanced mobile OS architectures - Presented by Jack Suann Trusted Firmware is inviting you to a scheduled Zoom meeting. Topic: TF-A Tech Forum Join Zoom Meeting https://linaro-org.zoom.us/j/93557863987?pwd=56a1l8cBnetDTZ6eazHGaE1Ctk4W34… Meeting ID: 935 5786 3987 Passcode: 939141 --- One tap mobile +12532158782,,93557863987# US (Tacoma) +13017158592,,93557863987# US (Washington DC) --- Dial by your location +1 253 215 8782 US (Tacoma) +1 301 715 8592 US (Washington DC) +1 305 224 1968 US +1 309 205 3325 US +1 312 626 6799 US (Chicago) +1 346 248 7799 US (Houston) +1 360 209 5623 US +1 386 347 5053 US +1 507 473 4847 US +1 564 217 2000 US +1 646 558 8656 US (New York) +1 646 931 3860 US +1 669 444 9171 US +1 669 900 9128 US (San Jose) +1 689 278 1000 US +1 719 359 4580 US +1 253 205 0468 US 833 548 0276 US Toll-free 833 548 0282 US Toll-free 833 928 4608 US Toll-free 833 928 4609 US Toll-free 833 928 4610 US Toll-free 877 853 5247 US Toll-free 888 788 0099 US Toll-free Meeting ID: 935 5786 3987 Find your local number: https://linaro-org.zoom.us/u/adoz9mILli TF-A Tech Forum Jan 22nd 10.00am -Part II Scaling Hafnium for advanced mobile OS architectures Thursday Jan 22, 2026 ⋅ 11am – 12pm Central European Time - Paris Location https://linaro-org.zoom.us/j/93557863987?pwd=56a1l8cBnetDTZ6eazHGaE1Ctk4W34… https://www.google.com/url?q=https%3A%2F%2Flinaro-org.zoom.us%2Fj%2F9355786… Hi, As follow up to the last session on Nov 13th 2025 [1], a new TF-A Tech Forum session with the topic'Scaling Hafnium for advanced mobile OS architectures' will be held on Jan 22nd 2026 10.00am. Regards,Olivier. [1] https://www.trustedfirmware.org/meetings/tf-a-technical-forum/ Scaling Hafnium for advanced mobile OS architectures - Presented by Jack Suann PDF Presentation Video Recording (Access Password: *PIs1^BD) Trusted Firmware is inviting you to a scheduled Zoom meeting.Topic: TF-A Tech ForumJoin Zoom Meetinghttps://linaro-org.zoom.us/j/93557863987?pwd=56a1l8cBnetDTZ6eazHGaE1Ctk4W34.1Meeting ID: 935 5786 3987Passcode: 939141---One tap mobile+12532158782,,93557863987# US (Tacoma)+13017158592,,93557863987# US (Washington DC)---Dial by your location• +1 253 215 8782 US (Tacoma)• +1 301 715 8592 US (Washington DC)• +1 305 224 1968 US• +1 309 205 3325 US• +1 312 626 6799 US (Chicago)• +1 346 248 7799 US (Houston)• +1 360 209 5623 US• +1 386 347 5053 US• +1 507 473 4847 US• +1 564 217 2000 US• +1 646 558 8656 US (New York)• +1 646 931 3860 US• +1 669 444 9171 US• +1 669 900 9128 US (San Jose)• +1 689 278 1000 US• +1 719 359 4580 US• +1 253 205 0468 US• 833 548 0276 US Toll-free• 833 548 0282 US Toll-free• 833 928 4608 US Toll-free• 833 928 4609 US Toll-free• 833 928 4610 US Toll-free• 877 853 5247 US Toll-free• 888 788 0099 US Toll-freeMeeting ID: 935 5786 3987Find your local number: https://linaro-org.zoom.us/u/adoz9mILli Guests tf-a(a)lists.trustedfirmware.org

6 days, 8 hours

1
0
0 0

New Defects reported by Coverity Scan for ARM-software/arm-trusted-firmware

by scan-admin＠coverity.com

Hi, Please find the latest report on new defect(s) introduced to ARM-software/arm-trusted-firmware found with Coverity Scan. 1 new defect(s) introduced to ARM-software/arm-trusted-firmware found with Coverity Scan. New defect(s) Reported-by: Coverity Scan Showing 1 of 1 defect(s) ** CID 501209: Control flow issues (DEADCODE) /lib/xlat_tables_v2/xlat_tables_core.c: 613 in xlat_tables_map_region() _____________________________________________________________________________________________ *** CID 501209: Control flow issues (DEADCODE) /lib/xlat_tables_v2/xlat_tables_core.c: 613 in xlat_tables_map_region() 607 608 table_base[table_idx] = 609 xlat_desc(ctx, (uint32_t)mm->attr, table_idx_pa, 610 level); 611 if (is_feat_morello_supported()) { 612 if (mm->attr & MT_CAP_LD_ST_TRACK) { >>> CID 501209: Control flow issues (DEADCODE) >>> Execution cannot reach this statement: "table_base[table_idx] |= 0x...". 613 table_base[table_idx] |= (SC_BIT | LC0_BIT); 614 } 615 } 616 617 } else if (action == ACTION_CREATE_NEW_TABLE) { 618 uintptr_t end_va; ________________________________________________________________________________________________________ To view the defects in Coverity Scan visit, https://scan.coverity.com/projects/arm-software-arm-trusted-firmware?tab=ov…

1 week

1
0
0 0

Trusted Firmware-A LTS v2.10.27 Release Announcement

by svc_openci_enginfra＠arm.com

Hello, Trusted Firmware-A LTS version 2.10.27 is now available. This release contains the following patches: fb0ca7ca1 build(npm): adhere to Husky deprecation notice [1] 17a8aec49 fix(cpus): workaround for Cortex-A76AE erratum 1931427 [2] fc5e6eeee fix(cpus): workaround for Cortex-A76AE erratum 1931435 [3] 918cb2542 fix(cpus): workaround for Cortex-A76AE erratum 1969401 [4] 6f78d7d29 fix(cpus): workaround for Cortex-A76AE erratum 2371140 [5] d5424f6d8 fix(build): set ERRATA_SPECULATIVE_AT after platform.mk [6] 659e46683 fix(cpus): workaround for Cortex-A65 erratum 1179935 [7] 909b29568 fix(cpus): workaround for Cortex-A65 erratum 1227419 [8] 42777038e fix(cpus): workaround for Cortex-A65 erratum 1541130 [9] 948f017ea fix(cpus): workaround for Cortex-A725 erratum 2874943 [10] 5ff59225e fix(cpus): workaround for Cortex-A725 erratum 2936490 [11] d2ab008e2 fix(cpus): workaround for Cortex-A725 erratum 3711914 [12] d0d0d0285 fix(cpus): workaround for Cortex-A725 erratum 3456106 [13] [1] https://review.trustedfirmware.org/q/I763a462b2a0da7852696f874df970810a2b01… [2] https://review.trustedfirmware.org/q/I31566838f894372e5627abda8b0bea1505f11… [3] https://review.trustedfirmware.org/q/I1baba8752f5f2e2ab5c873030e1f00cbb8cf1… [4] https://review.trustedfirmware.org/q/I893452450d430833e6c5a8e33a1e37b708218… [5] https://review.trustedfirmware.org/q/Id65846bebde1a0911ba11956202d0d255d3c8… [6] https://review.trustedfirmware.org/q/I221dab39c417531c5a148886d3e29709ba8b5… [7] https://review.trustedfirmware.org/q/Ie59a4897f849269a590d8fa2d25cceab5f2cb… [8] https://review.trustedfirmware.org/q/I42371e7d53fce3a7e085bf0b348f080fa323f… [9] https://review.trustedfirmware.org/q/I72498f60f8449193ed4b5b2a9e7a08530e786… [10] https://review.trustedfirmware.org/q/I686bbde8756d52afee92097ec05b97138b550… [11] https://review.trustedfirmware.org/q/I9833f8831ba3735a94763791a65be11b95c00… [12] https://review.trustedfirmware.org/q/If3b9d3a0f495b3a172d3e6e5ca7afa8c30aeb… [13] https://review.trustedfirmware.org/q/I10d1e8cb4da19ba4101a5617245ff75866707… Alternatively, Change Log is available in the documentation section: https://trustedfirmware-a.readthedocs.io/en/lts-v2.10.27/change-log.html Thanks, TF-A LTS team

1 week, 1 day

1
0
0 0

Email to TF-A

by Prasanth Nair

Email to TF-A

1 week, 1 day

1
0
0 0

Trusted Firmware-A LTS v2.8.41 Release Announcement

by svc_openci_enginfra＠arm.com

Hello, Trusted Firmware-A LTS version 2.8.41 is now available. This release contains the following patches: 0a85ca29f fix(security): add clrbhb support [1] 7c5bca9b9 fix(cpus): workaround for Cortex-A715 erratum 2409570 [2] 931417cff fix(cpus): workaround for Cortex-A715 erratum 2376701 [3] 368077598 fix(cpus): workaround for Cortex-A715 erratum 3711916 [4] 930fcc0b6 fix(cpus): workaround for Cortex-A76AE erratum 1931427 [5] 34f2ec4d0 fix(cpus): workaround for Cortex-A76AE erratum 1931435 [6] 9ad229ec8 fix(cpus): workaround for Cortex-A76AE erratum 1969401 [7] dccafbf14 fix(cpus): workaround for Cortex-A76AE erratum 2371140 [8] 24191cda2 fix(cpus): workaround for Cortex-A65 erratum 1179935 [9] ec702b29f fix(cpus): workaround for Cortex-A65 erratum 1227419 [10] 1cf89d221 fix(cpus): workaround for Cortex-A65 erratum 1541130 [11] a5b818591 docs(security): add CVE-2024-5660 and CVE-2024-7881 reference links [12] 800a3bda8 fix(security): update Cortex-X4 fix version for CVE-2024-7881 [13] e3eed549b fix(security): update Neoverse-V3/V3AE fix version for CVE-2024-7881 [14] e56910a48 fix(security): update Cortex-X3 fix version for CVE-2024-7881 [15] 76e43568c fix(security): update Neoverse-V2 fix version for CVE-2024-7881 [16] 8776324c8 docs(security): update CVE-2024-7881 affected CPU revisions [17] 990086206 fix(cpus): register ARCH_WORKAROUND_3 for Neoverse V2 [18] ba8c49193 fix(cpus): workaround for Cortex-A710 erratum 3324338 [19] b4cdfa94d fix(cpus): workaround for Cortex-X2 erratum 3324338 [20] d3169c509 fix(cpus): workaround for Cortex-A715 erratum 3456084 [21] bddc18aea fix(cpus): workaround for Cortex-A720 erratum 3456091 [22] [1] https://review.trustedfirmware.org/q/Ie6e56e96378503456a1617d5e5d51bc64c2e0… [2] https://review.trustedfirmware.org/q/Id9429831525b842779d7b7e60f103c93be4ac… [3] https://review.trustedfirmware.org/q/Idcd2a07d269d55534dc5faa59c454d37426f2… [4] https://review.trustedfirmware.org/q/Iad149a2c02a804b3f4f0f2f5b89e866675cb4… [5] https://review.trustedfirmware.org/q/I31566838f894372e5627abda8b0bea1505f11… [6] https://review.trustedfirmware.org/q/I1baba8752f5f2e2ab5c873030e1f00cbb8cf1… [7] https://review.trustedfirmware.org/q/I893452450d430833e6c5a8e33a1e37b708218… [8] https://review.trustedfirmware.org/q/Id65846bebde1a0911ba11956202d0d255d3c8… [9] https://review.trustedfirmware.org/q/Ie59a4897f849269a590d8fa2d25cceab5f2cb… [10] https://review.trustedfirmware.org/q/I42371e7d53fce3a7e085bf0b348f080fa323f… [11] https://review.trustedfirmware.org/q/I72498f60f8449193ed4b5b2a9e7a08530e786… [12] https://review.trustedfirmware.org/q/Ia3c003d5c359f101f230fbd54845f61117456… [13] https://review.trustedfirmware.org/q/Iae84f26fdce96a61fdc942b7595ccf8b9c778… [14] https://review.trustedfirmware.org/q/If3e2989a4b5a5c68dc12e23978b226c73f21b… [15] https://review.trustedfirmware.org/q/Ia1ff75602a0dfa758a223549d92ea87543fa4… [16] https://review.trustedfirmware.org/q/I1ae196fa8ce4579524faba4916f631e7c4db3… [17] https://review.trustedfirmware.org/q/Iad109561a144169fd3805c179a4f8e3bfdd59… [18] https://review.trustedfirmware.org/q/I8c08c26e0b7c268772d75d36d759564a7d67c… [19] https://review.trustedfirmware.org/q/I9325f3715f4fa17bfb7ded9d5c69c59645f65… [20] https://review.trustedfirmware.org/q/Ibbe55a55bd6cf5e159dab92a78ecb55c5a4d7… [21] https://review.trustedfirmware.org/q/Ie3f2b46051539cdebc151c46f80045a7156e0… [22] https://review.trustedfirmware.org/q/Ia22a0d6bb98d1a0edb11d2469beab22c7f7ab… Alternatively, Change Log is available in the documentation section: https://trustedfirmware-a.readthedocs.io/en/lts-v2.8.41/change-log.html Thanks, TF-A LTS team

1 week, 5 days

1
0
0 0

ZynqMP regression with NUMA_AWARE_PER_CPU changes with ENABLED_LTO : Linux runtime hang due to EL3 re-entry

by Kummari, Prasad

[AMD Official Use Only - AMD Internal Distribution Only] Hello Maintainers, We are observing a reproducible runtime regression on the ZynqMP (Cortex-A53) platform after enabling LTO (ENABLED_LTO=1) and merging the changes from the topic NUMA_AWARE_PER_CPU into our integration branch (https://github.com/ARM-software/arm-trusted-firmware/commit/7303319b3823e9e…). Summary of the issue 1. Baseline behavior * Platform: ZynqMP (Cortex-A53) * Configuration: ENABLED_LTO=1 * Without NUMA_AWARE_PER_CPU: Linux boots and runs stably * After merging NUMA_AWARE_PER_CPU, Linux boots but hangs during runtime * During the hang, CPUs are observed to unexpectedly re-enter EL3 * Re-entry into EL3 should not occur during normal Linux runtime execution and strongly suggests corruption or mismanagement of PSCI and/or per-CPU state(arm-trusted-firmware/lib/per_cpu/aarch64/per_cpu_asm.S at master * ARM-software/arm-trusted-firmware<https://github.com/ARM-software/arm-trusted-firmware/blob/master/lib/per_cp…>) * Reverting the NUMA_AWARE_PER_CPU changes restores stable Linux execution * The issue is reproducible only when NUMA_AWARE_PER_CPU is present * This clearly identifies NUMA_AWARE_PER_CPU as the regression source 2. Suspect with LTO * With NUMA_AWARE_PER_CPU enabled, LTO breaks the per-CPU base calculation * BL31 contains hand-written assembly that relies on linker-script symbols (e.g., per-CPU section boundaries) * Under LTO, symbol placement and retention are no longer guaranteed in the same way, leading to incorrect per-CPU base computation * This results in corrupted per-CPU data and subsequent erroneous PSCI suspend behavior (EL3 re-entry) 3. CPU idle dependency * The following kernel configuration options are enabled: * CONFIG_CPU_IDLE=y * CONFIG_CPU_IDLE_MULTIPLE_DRIVERS=y * CONFIG_CPU_IDLE_GOV_MENU=y * CONFIG_DT_IDLE_STATES=y * This further suggests the issue is triggered during CPU idle / suspend-resume paths, where correct per-CPU state handling is critical Based on the above: * This is specific to NUMA_AWARE_PER_CPU combined with LTO * The failure mode points to per-CPU base calculation and PSCI state corruption * Reverting NUMA_AWARE_PER_CPU fully restores stability on ZynqMP We wanted to report this issue upstream and seek guidance on: * Whether NUMA_AWARE_PER_CPU is expected to be LTO-safe on platforms relying on linker-defined per-CPU sections * Or if additional constraints / fixes are required for platforms like ZynqMP We are happy to provide further logs, configuration details, or help to fixes. Regards, Prasad Kummari

1 week, 6 days

2
7
0 0

Canceled event with note: TF-A Tech Forum @ Thu Jan 8, 2026 5pm - 6pm (GMT+1) (tf-a@lists.trustedfirmware.org)

by Olivier Deprez

This event has been canceled with a note: "Cancelling as no topic this week." TF-A Tech Forum Thursday Jan 8, 2026 ⋅ 5pm – 6pm Central European Time - Paris Location https://linaro-org.zoom.us/j/93557863987?pwd=56a1l8cBnetDTZ6eazHGaE1Ctk4W34… https://www.google.com/url?q=https%3A%2F%2Flinaro-org.zoom.us%2Fj%2F9355786… Trusted Firmware is inviting you to a scheduled Zoom meeting.Topic: TF-A Tech ForumTime: May 15, 2025 02:00 PM London Every 2 weeks on Thu, 78 occurrence(s)Please download and import the following iCalendar (.ics) files to your calendar system.Weekly: https://linaro-org.zoom.us/meeting/tJcocu6gqDgjEtOkyBhSQauR1sUyFwIcNKLa/ics… Zoom Meetinghttps://linaro-org.zoom.us/j/93557863987?pwd=56a1l8cBnetDTZ6eazHGaE1Ctk4W34.1Meeting ID: 935 5786 3987Passcode: 939141---One tap mobile+12532158782,,93557863987# US (Tacoma)+13017158592,,93557863987# US (Washington DC)---Dial by your location• +1 253 215 8782 US (Tacoma)• +1 301 715 8592 US (Washington DC)• +1 305 224 1968 US• +1 309 205 3325 US• +1 312 626 6799 US (Chicago)• +1 346 248 7799 US (Houston)• +1 360 209 5623 US• +1 386 347 5053 US• +1 507 473 4847 US• +1 564 217 2000 US• +1 646 558 8656 US (New York)• +1 646 931 3860 US• +1 669 444 9171 US• +1 669 900 9128 US (San Jose)• +1 689 278 1000 US• +1 719 359 4580 US• +1 253 205 0468 US• 833 548 0276 US Toll-free• 833 548 0282 US Toll-free• 833 928 4608 US Toll-free• 833 928 4609 US Toll-free• 833 928 4610 US Toll-free• 877 853 5247 US Toll-free• 888 788 0099 US Toll-freeMeeting ID: 935 5786 3987Find your local number: https://linaro-org.zoom.us/u/adoz9mILli Guests qwandor(a)google.com praan(a)google.com jeremimiller(a)google.com jagdish.gediya(a)linaro.org tf-a(a)lists.trustedfirmware.org ~~//~~ Invitation from Google Calendar: https://calendar.google.com/calendar/ You are receiving this email because you are an attendee on the event. Forwarding this invitation could allow any recipient to send a response to the organizer, be added to the guest list, invite others regardless of their own invitation status, or modify your RSVP. Learn more https://support.google.com/calendar/answer/37135#forwarding

1 week, 6 days

1
0
0 0

Invitation: TF-A Tech Forum Jan 22nd 10.00am -Part II Scaling Hafnium... @ Thu Jan 22, 2026 11am - 12pm (GMT+1) (tf-a@lists.trustedfirmware.org)

by Olivier Deprez

TF-A Tech Forum Jan 22nd 10.00am -Part II Scaling Hafnium for advanced mobile OS architectures Thursday Jan 22, 2026 ⋅ 11am – 12pm Central European Time - Paris Location https://linaro-org.zoom.us/j/93557863987?pwd=56a1l8cBnetDTZ6eazHGaE1Ctk4W34… https://www.google.com/url?q=https%3A%2F%2Flinaro-org.zoom.us%2Fj%2F9355786… Hi, As follow up to the last session on Nov 13th 2025 [1], a new TF-A Tech Forum session with the topic'Scaling Hafnium for advanced mobile OS architectures' will be held on Jan 22nd 2026 10.00am. Regards,Olivier. [1] https://www.trustedfirmware.org/meetings/tf-a-technical-forum/ Scaling Hafnium for advanced mobile OS architectures - Presented by Jack Suann PDF Presentation Video Recording (Access Password: *PIs1^BD) Trusted Firmware is inviting you to a scheduled Zoom meeting.Topic: TF-A Tech ForumJoin Zoom Meetinghttps://linaro-org.zoom.us/j/93557863987?pwd=56a1l8cBnetDTZ6eazHGaE1Ctk4W34.1Meeting ID: 935 5786 3987Passcode: 939141---One tap mobile+12532158782,,93557863987# US (Tacoma)+13017158592,,93557863987# US (Washington DC)---Dial by your location• +1 253 215 8782 US (Tacoma)• +1 301 715 8592 US (Washington DC)• +1 305 224 1968 US• +1 309 205 3325 US• +1 312 626 6799 US (Chicago)• +1 346 248 7799 US (Houston)• +1 360 209 5623 US• +1 386 347 5053 US• +1 507 473 4847 US• +1 564 217 2000 US• +1 646 558 8656 US (New York)• +1 646 931 3860 US• +1 669 444 9171 US• +1 669 900 9128 US (San Jose)• +1 689 278 1000 US• +1 719 359 4580 US• +1 253 205 0468 US• 833 548 0276 US Toll-free• 833 548 0282 US Toll-free• 833 928 4608 US Toll-free• 833 928 4609 US Toll-free• 833 928 4610 US Toll-free• 877 853 5247 US Toll-free• 888 788 0099 US Toll-freeMeeting ID: 935 5786 3987Find your local number: https://linaro-org.zoom.us/u/adoz9mILli Guests tf-a(a)lists.trustedfirmware.org View all guest info https://calendar.google.com/calendar/event?action=VIEW&eid=NmFoYTlsdXBjYjZj… Reply for tf-a(a)lists.trustedfirmware.org and view more details https://calendar.google.com/calendar/event?action=VIEW&eid=NmFoYTlsdXBjYjZj… Your attendance is optional. ~~//~~ Invitation from Google Calendar: https://calendar.google.com/calendar/ You are receiving this email because you are an attendee on the event. Forwarding this invitation could allow any recipient to send a response to the organizer, be added to the guest list, invite others regardless of their own invitation status, or modify your RSVP. Learn more https://support.google.com/calendar/answer/37135#forwarding

1 week, 6 days

1
0
0 0

New Defects reported by Coverity Scan for ARM-software/arm-trusted-firmware

by scan-admin＠coverity.com

Hi, Please find the latest report on new defect(s) introduced to ARM-software/arm-trusted-firmware found with Coverity Scan. 1 new defect(s) introduced to ARM-software/arm-trusted-firmware found with Coverity Scan. 1 defect(s), reported by Coverity Scan earlier, were marked fixed in the recent build analyzed by Coverity Scan. New defect(s) Reported-by: Coverity Scan Showing 1 of 1 defect(s) ** CID 501137: Integer handling issues (CONSTANT_EXPRESSION_RESULT) /common/runtime_svc.c: 261 in handler_sync_exception() _____________________________________________________________________________________________ *** CID 501137: Integer handling issues (CONSTANT_EXPRESSION_RESULT) /common/runtime_svc.c: 261 in handler_sync_exception() 255 /* advance the PC to continue after the instruction */ 256 write_ctx_reg(state, CTX_ELR_EL3, read_ctx_reg(state, CTX_ELR_EL3) + 4); 257 } /* otherwise return to the trapping instruction (repeating it) */ 258 return; 259 /* If FFH Support then try to handle lower EL EA exceptions. */ 260 } else if ((exc_class == EC_IABORT_LOWER_EL || exc_class == EC_DABORT_LOWER_EL) >>> CID 501137: Integer handling issues (CONSTANT_EXPRESSION_RESULT) >>> "state->ctx_regs[0U /* 0U >> 3U */] | (8UL /* 1UL << 3 */)" is always 1/true regardless of the values of its operand. This occurs as the logical second operand of "&&". 261 && (read_ctx_reg(state, CTX_SCR_EL3) | SCR_EA_BIT)) { 262 #if FFH_SUPPORT 263 /* 264 * Check for Uncontainable error type. If so, route to the 265 * platform fatal error handler rather than the generic EA one. 266 */ ________________________________________________________________________________________________________ To view the defects in Coverity Scan visit, https://scan.coverity.com/projects/arm-software-arm-trusted-firmware?tab=ov…

2 weeks

1
0
0 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

TF-A January 2026