- TF-A - lists.trustedfirmware.org

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 506142: Memory - corruptions (OVERRUN) _____________________________________________________________________________________________ *** CID 506142: Memory - corruptions (OVERRUN) /plat/rpi/rpi3/rpi3_bl1_mboot.c: 178 in bl1_plat_mboot_init() 172 tpm_alg_query_t alg_query[] = { 173 { .alg_id = TPM_ALG_SHA256 }, 174 { .alg_id = EVLOG_TPM_ALG_SHA384 }, 175 { .alg_id = EVLOG_TPM_ALG_SHA512 }, 176 { .alg_id = TPM_ALG_NULL }, 177 }; >>> CID 506142: Memory - corruptions (OVERRUN) >>> Overrunning array "alg_query" of 4 4-byte elements by passing it to a function which accesses it at element index 63 (byte offset 255). 178 rc = tpm_getcap_query_algs(&tpm_chip_data, alg_query); 179 if (rc < 0) { 180 ERROR("Failed to query TPM algs (%d).\n", rc); 181 panic(); 182 } 183 ________________________________________________________________________________________________________ To view the defects in Coverity Scan visit, https://scan.coverity.com/projects/arm-software-arm-trusted-firmware?tab=ov…

1 month, 2 weeks

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. 5 new defect(s) introduced to ARM-software/arm-trusted-firmware found with Coverity Scan. New defect(s) Reported-by: Coverity Scan Showing 5 of 5 defect(s) ** CID 506049: Insecure data handling (TAINTED_SCALAR) /home/buildslave/agent/workspace/tf-a-coverity/trusted-firmware-a/contrib/libtpm/src/tpm2_cmds.c: 568 in parse_pcrs_find() _____________________________________________________________________________________________ *** CID 506049: Insecure data handling (TAINTED_SCALAR) /home/buildslave/agent/workspace/tf-a-coverity/trusted-firmware-a/contrib/libtpm/src/tpm2_cmds.c: 568 in parse_pcrs_find() 562 if (ret != TPM_SUCCESS) { 563 return ret; 564 } 565 566 iter_read_u32_be(&iter, &count); 567 >>> CID 506049: Insecure data handling (TAINTED_SCALAR) >>> Using tainted variable "count" as a loop boundary. 568 for (uint32_t i = 0U; i < count; i++) { 569 iter_read_u16_be(&iter, &hash_id); 570 iter_read_u8(&iter, &sizeof_select); 571 if (iter.error_state != TPM_SUCCESS) { 572 return iter.error_state; 573 } ** CID 506048: Memory - corruptions (OVERRUN) _____________________________________________________________________________________________ *** CID 506048: Memory - corruptions (OVERRUN) /home/buildslave/agent/workspace/tf-a-coverity/trusted-firmware-a/contrib/libtpm/src/tpm2_cmds.c: 1071 in tpm_has_alg() 1065 } 1066 1067 item[0].alg_id = alg_id; 1068 item[0].enabled = false; 1069 item[1].alg_id = TPM_ALG_NULL; 1070 item[1].enabled = false; >>> CID 506048: Memory - corruptions (OVERRUN) >>> Overrunning array "item" of 2 4-byte elements by passing it to a function which accesses it at element index 63 (byte offset 255). 1071 ret = tpm_getcap_query_algs(chip, item); 1072 if (ret != TPM_SUCCESS) { 1073 return ret; 1074 } 1075 1076 *out_supported = item[0].enabled; ** CID 506047: Insecure data handling (TAINTED_SCALAR) /home/buildslave/agent/workspace/tf-a-coverity/trusted-firmware-a/contrib/libtpm/src/tpm2_cmds.c: 444 in parse_algs_find() _____________________________________________________________________________________________ *** CID 506047: Insecure data handling (TAINTED_SCALAR) /home/buildslave/agent/workspace/tf-a-coverity/trusted-firmware-a/contrib/libtpm/src/tpm2_cmds.c: 444 in parse_algs_find() 438 if (ret != TPM_SUCCESS) { 439 return ret; 440 } 441 442 iter_read_u32_be(&iter, &count); 443 >>> CID 506047: Insecure data handling (TAINTED_SCALAR) >>> Using tainted variable "count" as a loop boundary. 444 for (uint32_t i = 0U; i < count; i++) { 445 iter_read_u16_be(&iter, &alg); 446 iter_read_u32_be(&iter, &props); 447 if (iter.error_state != TPM_SUCCESS) { 448 return iter.error_state; 449 } ** CID 506046: Insecure data handling (TAINTED_SCALAR) /home/buildslave/agent/workspace/tf-a-coverity/trusted-firmware-a/contrib/libtpm/src/tpm2_cmds.c: 386 in parse_algs() _____________________________________________________________________________________________ *** CID 506046: Insecure data handling (TAINTED_SCALAR) /home/buildslave/agent/workspace/tf-a-coverity/trusted-firmware-a/contrib/libtpm/src/tpm2_cmds.c: 386 in parse_algs() 380 if (ret != TPM_SUCCESS) { 381 return ret; 382 } 383 384 iter_read_u32_be(&iter, &count); 385 >>> CID 506046: Insecure data handling (TAINTED_SCALAR) >>> Using tainted variable "count" as a loop boundary. 386 for (uint32_t i = 0U; i < count; i++) { 387 iter_read_u16_be(&iter, &alg); 388 iter_read_u32_be(&iter, &properties); 389 if (iter.error_state != TPM_SUCCESS) { 390 return iter.error_state; 391 } ** CID 506045: Insecure data handling (TAINTED_SCALAR) /home/buildslave/agent/workspace/tf-a-coverity/trusted-firmware-a/contrib/libtpm/src/tpm2_cmds.c: 498 in parse_pcrs() _____________________________________________________________________________________________ *** CID 506045: Insecure data handling (TAINTED_SCALAR) /home/buildslave/agent/workspace/tf-a-coverity/trusted-firmware-a/contrib/libtpm/src/tpm2_cmds.c: 498 in parse_pcrs() 492 if (ret != TPM_SUCCESS) { 493 return ret; 494 } 495 496 iter_read_u32_be(&iter, &count); 497 >>> CID 506045: Insecure data handling (TAINTED_SCALAR) >>> Using tainted variable "count" as a loop boundary. 498 for (uint32_t i = 0U; i < count; i++) { 499 iter_read_u16_be(&iter, &hash); 500 iter_read_u8(&iter, &sizeof_select); 501 if (iter.error_state != TPM_SUCCESS) { 502 return iter.error_state; 503 } ________________________________________________________________________________________________________ To view the defects in Coverity Scan visit, https://scan.coverity.com/projects/arm-software-arm-trusted-firmware?tab=ov…

1 month, 2 weeks

1
0
0 0

Trusted Firmware-A LTS v2.14.8 Release Announcement

by svc_openci_enginfra＠arm.com

Hello, Trusted Firmware-A LTS version 2.14.8 is now available. This release contains the following patches: 23a043ecf refactor(cpus): align AE variant core names [1] 06e6a11cd feat(cpus): add links to each core's TRM and SDEN [2] e808effb2 fix(cpus): use #ifdef for IMAGE_BL flags [3] d88a86de0 refactor(cpus): factor out Neoverse V3AE from the base Neoverse V3 file [4] b1636c347 fix(rdaspen): enable A720AE erratum 3456103 [5] 9bf7047a4 feat(psci): add hierarchical power state consistency check [6] 71d0777fd fix(psci): validate last_at_pwrlvl bounds before use [7] 35bb2bf98 fix(arm): validate last_at_pwrlvl before forwarding it [8] e5d084678 fix(fdt-wrappers): reject negative cell counts [9] dc4d9feab fix(el3-spmc): harden composite MRD validation [10] ffd31a2bc fix(rk3568): implement CPU core suspend/resume power domain hooks [11] d502f6dd9 chore(deps): add LTS-v2.14 Dependabot configuration [12] 68d99c69b docs: add LTS Dependabot release step [13] [1] https://review.trustedfirmware.org/q/I999ed43421d083af148c3e92cef9d8ca5c635… [2] https://review.trustedfirmware.org/q/I6fe089876aa2d764a67733041751202e2bd3c… [3] https://review.trustedfirmware.org/q/I5a4e2acdd007ba56039b992bde77d2a940030… [4] https://review.trustedfirmware.org/q/Ic658273bd4502c28281a7963a8c862c26da64… [5] https://review.trustedfirmware.org/q/Ia3f25dd8943a99563b95695f5f505a297997f… [6] https://review.trustedfirmware.org/q/Iee25103004bd424fb498e6b23b0f88b2abcc7… [7] https://review.trustedfirmware.org/q/I0d7b679ced6d17274dfcc5d57f50e8021bdba… [8] https://review.trustedfirmware.org/q/I0a0dbc9e60713796b99bc4b9d11b403671c0e… [9] https://review.trustedfirmware.org/q/I67bf1e5773211df80d3b8ba71157a87d70ce2… [10] https://review.trustedfirmware.org/q/I207d2fe57766bee83a7c4c8b51f259b08934b… [11] https://review.trustedfirmware.org/q/Icc20759ef18900a0702bc2345ad768a2dd63b… [12] https://review.trustedfirmware.org/q/I68fe77580b13c9bb2f1e04cea79ebba01c9f6… [13] https://review.trustedfirmware.org/q/I22cfbf65449e4b32d5ba2a39bbac89e0fd2ab… Alternatively, Change Log is available in the documentation section: https://trustedfirmware-a.readthedocs.io/en/lts-v2.14.8/change-log.html Thanks, TF-A LTS team

1 month, 2 weeks

1
0
0 0

Trusted Firmware-A LTS v2.10.35 Release Announcement

by svc_openci_enginfra＠arm.com

Hello, Trusted Firmware-A LTS version 2.10.35 is now available. This release contains the following patches: 48ae48d0c fix(intel): update fcs crypto init code to check for mode [1] 6e6cc3ec2 fix(imx8m): don't reconfigure default region0 [2] f60721cab fix(xilinx): enforce volatile call status vars [3] 5b1aa78b6 fix(tools): change data type to size_t for doimage [4] 0958da979 build(deps): bump the npm_and_yarn group across 1 directory with 5 updates [5] 81eab6d80 refactor(cpus): align AE variant core names [6] 6f951de87 feat(cpus): add links to each core's TRM and SDEN [7] 2fe5d6a71 fix(cpus): use #ifdef for IMAGE_BL flags [8] d4cfb4dc5 refactor(cpus): factor out Neoverse V3AE from the base Neoverse V3 file [9] 289e785d9 fix(psci): modify variable conflicting with external function [10] 511450d3c fix(psci): add missing curly braces [11] cc5495c5d feat(psci): add hierarchical power state consistency check [12] cd8294878 fix(psci): validate last_at_pwrlvl bounds before use [13] 083009355 fix(arm): validate last_at_pwrlvl before forwarding it [14] 9b53aab02 docs: add LTS Dependabot release step [15] 353c4fe1d fix(fdt-wrappers): reject negative cell counts [16] 810363985 fix(el3-spmc): harden composite MRD validation [17] [1] https://review.trustedfirmware.org/q/I702ce90e229188830f8936bee2999610e9559… [2] https://review.trustedfirmware.org/q/I0a0f9b5ad0017f38d767f583d7765a2f79861… [3] https://review.trustedfirmware.org/q/I40deb494ad6d03b9640673044687a4a83c1f7… [4] https://review.trustedfirmware.org/q/I658521c1eec1c79933ba8082ba507df04d174… [5] https://review.trustedfirmware.org/q/I3203e9eb23315f2442e3715549f7541207fe4… [6] https://review.trustedfirmware.org/q/I999ed43421d083af148c3e92cef9d8ca5c635… [7] https://review.trustedfirmware.org/q/I6fe089876aa2d764a67733041751202e2bd3c… [8] https://review.trustedfirmware.org/q/I5a4e2acdd007ba56039b992bde77d2a940030… [9] https://review.trustedfirmware.org/q/Ic658273bd4502c28281a7963a8c862c26da64… [10] https://review.trustedfirmware.org/q/I2f109242b6dd3b3c5e9289881e3dd5466c74f… [11] https://review.trustedfirmware.org/q/Ida2460b7fe6f27b23382a1259a5ac93fe36bd… [12] https://review.trustedfirmware.org/q/Iee25103004bd424fb498e6b23b0f88b2abcc7… [13] https://review.trustedfirmware.org/q/I0d7b679ced6d17274dfcc5d57f50e8021bdba… [14] https://review.trustedfirmware.org/q/I0a0dbc9e60713796b99bc4b9d11b403671c0e… [15] https://review.trustedfirmware.org/q/I22cfbf65449e4b32d5ba2a39bbac89e0fd2ab… [16] https://review.trustedfirmware.org/q/I67bf1e5773211df80d3b8ba71157a87d70ce2… [17] https://review.trustedfirmware.org/q/I207d2fe57766bee83a7c4c8b51f259b08934b… Alternatively, Change Log is available in the documentation section: https://trustedfirmware-a.readthedocs.io/en/lts-v2.10.35/change-log.html Thanks, TF-A LTS team

1 month, 2 weeks

1
0
0 0

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

by Olivier Deprez

This event has been canceled with a note: "Hi cancelling as no topic planned. Regards, Olivier. " TF-A Tech Forum Thursday Sep 17, 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 Forum Time: 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… 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 Guests d82620130(a)gmail.com namyoon(a)google.com shaikadnanafrid(a)gmail.com tf-a(a)lists.trustedfirmware.org ~~//~~ Sent by 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 month, 3 weeks

1
0
0 0

Process for Platform-Specific LTS Candidate Patches in TF-A

by Manish Badarkhe

Hi, I would like to share the process to follow for patches that are considered candidates for TF-A LTS branches. When submitting a patch to the TF-A `integration` branch that is expected to be backported to an LTS branch, please follow the TF-A contribution guidance and add the following tag to the commit message footer: `LTS-candidate: yes` The contribution guidance is available here: https://trustedfirmware-a.readthedocs.io/en/latest/process/contributing.htm… The `LTS-candidate: yes` tag indicates that the patch is considered relevant for backporting to applicable LTS branches. Once an LTS-candidate patch has been merged into `integration`, if the patch is relevant to a particular platform, it would be appreciated if the respective platform owner/maintainer could cherry-pick and submit the patch to the applicable LTS branch(es), adding the LTS maintainers as reviewers. The list of LTS maintainers is available here: https://trustedfirmware-a.readthedocs.io/en/latest/about/maintainers.html#l… This should help ensure that LTS-relevant changes are appropriately carried over, while allowing platform-specific backports to be handled and validated by the maintainers most familiar with those platforms. Thanks for your cooperation. Please let us know if you have any questions regarding this process. Thanks, Manish Badarkhe

1 month, 3 weeks

1
0
0 0

Trusted Firmware-A LTS v2.14.7 Release Announcement

by svc_openci_enginfra＠arm.com

Hello, Trusted Firmware-A LTS version 2.14.7 is now available. This release contains the following patches: 670b014e9 fix(qti): restrict EUD register r/w to debug builds only [1] 8afa01feb fix(qti): do not map secure regions [2] 5b7e825cc fix(qti): disallow secure IO accesses from secure world callers [3] 72d0f09ed fix(qti): pull in access-control backend for mem_assign [4] ebe3bfdd3 fix(qti): harden mem_assign parameter handling [5] 329b63a1e fix(cpus): workaround for Neoverse V2 erratum 2394277 [6] 26d172be2 fix(cpus): enable Neoverse-V2 external LLC support [7] 521c2a0b8 fix(cpus): remove duplicate comments from lib/cpus/cpu-ops.mk [8] 508e466c0 fix(cpus): workaround for C1-Pro erratum 3773617 [9] 9b42e88ad fix(build): fix misapplication of errata A53 843419 [10] 9d56fd145 fix(cpus): add workaround for Cortex-A510 erratum 4568615 [11] 85c538676 fix(cpus): add workaround for Cortex-A520 erratum 4491980 [12] fc7017a81 fix(cpus): add workaround for C1-Nano erratum 4497400 [13] 306b56722 docs(xlat): add erratum 3683289 comments [14] a0cf2dfba docs(cpus): add erratum 4015814 comments [15] [1] https://review.trustedfirmware.org/q/Iee82e60ef2b3182f6ebd542611d909e06339d… [2] https://review.trustedfirmware.org/q/I070bb347039e467c1407cf6ceb832e43e7512… [3] https://review.trustedfirmware.org/q/I6dea64e110184f73868ac188fca2d755999d5… [4] https://review.trustedfirmware.org/q/Ia84fd78b62ea5e7e7e7b9fa85d6baf1ab04b5… [5] https://review.trustedfirmware.org/q/Ie9e5480891a82ba98919c8c7dbdd27819e246… [6] https://review.trustedfirmware.org/q/Ib1ec35e313deddd1e19eabc1fd36968d542d7… [7] https://review.trustedfirmware.org/q/I9582c7405db6862e77db240822e241d408296… [8] https://review.trustedfirmware.org/q/Ice03a0f2932e97e2734aa36e7dd7f9764cf28… [9] https://review.trustedfirmware.org/q/I9b83add5d104f4621520c8e90777f10c7a97d… [10] https://review.trustedfirmware.org/q/Ifffc683c0a5253a1085e1a1c2a2203950a232… [11] https://review.trustedfirmware.org/q/I00b76de0a51e60b818c271c6341bcf6682e25… [12] https://review.trustedfirmware.org/q/I69e7ead39200c627461ae4d54b2b291579605… [13] https://review.trustedfirmware.org/q/I6ca4b63ca187fe17dc317e10ec3b4b42fdab1… [14] https://review.trustedfirmware.org/q/Idb4a6f864967b25b5187dd882fb47abfa2bc4… [15] https://review.trustedfirmware.org/q/I899d1c54cf152159e494a73f7fa962eab32d4… Alternatively, Change Log is available in the documentation section: https://trustedfirmware-a.readthedocs.io/en/lts-v2.14.7/change-log.html Thanks, TF-A LTS team

1 month, 3 weeks

1
0
0 0

Trusted Firmware-A LTS v2.12.15 Release Announcement

by svc_openci_enginfra＠arm.com

Hello, Trusted Firmware-A LTS version 2.12.15 is now available. This release contains the following patches: fc6a2cbd5 fix(cpus): workaround for C1-Pro erratum 3773617 [1] 9126701a2 fix(cpus): add workaround for Cortex-A510 erratum 4568615 [2] 61553a9a2 fix(cpus): add workaround for Cortex-A520 erratum 4491980 [3] 0e52b50b2 fix(cpus): add workaround for C1-Nano erratum 4497400 [4] 3ec9c78b0 fix(docs): fix some broken links [5] 789ffc7b3 fix(cpus): remove duplicate comments from lib/cpus/cpu-ops.mk [6] a1e77604d docs(xlat): add erratum 3683289 comments [7] 8412c2855 docs(cpus): add erratum 4015814 comments [8] 8022db055 fix(xilinx): enforce volatile call status vars [9] 326307098 fix(el3-spmc): prevent integer overflow in memory overlap validation [10] 9cb9d6fed fix(guid-partition): harden backup GPT loading [11] ce1185549 build(deps): bump igraph from 0.11.6 to 0.11.8 in /tools/cot_dt2c [12] ed3c5dda3 build(deps-dev): bump pytest from 8.3.4 to 8.3.5 in /tools/cot_dt2c [13] fd5e53f8f build(deps-dev): bump pytest from 8.3.3 to 8.3.5 in /tools/tlc [14] 8c33e76ba build(deps-dev): bump bandit from 1.7.9 to 1.7.10 in /tools/tlc [15] ad69789cf build(deps): bump tox from 4.20.0 to 4.25.0 in /tools/tlc [16] d2eb457b2 build(deps-dev): bump commitizen [17] [1] https://review.trustedfirmware.org/q/I9b83add5d104f4621520c8e90777f10c7a97d… [2] https://review.trustedfirmware.org/q/I00b76de0a51e60b818c271c6341bcf6682e25… [3] https://review.trustedfirmware.org/q/I69e7ead39200c627461ae4d54b2b291579605… [4] https://review.trustedfirmware.org/q/I6ca4b63ca187fe17dc317e10ec3b4b42fdab1… [5] https://review.trustedfirmware.org/q/I384094c8dcf3e93875c9052afa79ad826b990… [6] https://review.trustedfirmware.org/q/Ice03a0f2932e97e2734aa36e7dd7f9764cf28… [7] https://review.trustedfirmware.org/q/Idb4a6f864967b25b5187dd882fb47abfa2bc4… [8] https://review.trustedfirmware.org/q/I899d1c54cf152159e494a73f7fa962eab32d4… [9] https://review.trustedfirmware.org/q/I40deb494ad6d03b9640673044687a4a83c1f7… [10] https://review.trustedfirmware.org/q/I7b16a3267f1fefafa3207b7d66fd6fb8aa30b… [11] https://review.trustedfirmware.org/q/I090b888c4acb45c119552fb236343ac10d3c8… [12] https://review.trustedfirmware.org/q/Icdff20c79e80d2e28243238465aa0a82aea86… [13] https://review.trustedfirmware.org/q/Ic00e1f7f3eed0c15efa4aad2be5d65d9b0c03… [14] https://review.trustedfirmware.org/q/I7ca2856751eb8de70042b4626581ee1d028a8… [15] https://review.trustedfirmware.org/q/Ied911c87232dde44eccde745a3e8c8ef9784d… [16] https://review.trustedfirmware.org/q/I2301600ad946368ad6cabec6badd752ab0fec… [17] https://review.trustedfirmware.org/q/Ib18c0496ce0dae554509ec80247da0a630f15… Alternatively, Change Log is available in the documentation section: https://trustedfirmware-a.readthedocs.io/en/lts-v2.12.15/change-log.html Thanks, TF-A LTS team

1 month, 3 weeks

1
0
0 0

Trusted Firmware-A LTS v2.8.46 Release Announcement

by svc_openci_enginfra＠arm.com

Hello, Trusted Firmware-A LTS version 2.8.46 is now available. This release contains the following patches: 1a52c0761 fix(intel): update fcs crypto init code to check for mode [1] fc38a9df1 fix(tools): change data type to size_t for doimage [2] e576443dd fix(imx8m): don't reconfigure default region0 [3] b741ab045 fix(el3-spmc): prevent integer overflow in memory overlap validation [4] 8efc140e0 fix(guid-partition): harden backup GPT loading [5] 4c689a4d7 fix(xilinx): enforce volatile call status vars [6] [1] https://review.trustedfirmware.org/q/I702ce90e229188830f8936bee2999610e9559… [2] https://review.trustedfirmware.org/q/I658521c1eec1c79933ba8082ba507df04d174… [3] https://review.trustedfirmware.org/q/I0a0f9b5ad0017f38d767f583d7765a2f79861… [4] https://review.trustedfirmware.org/q/I7b16a3267f1fefafa3207b7d66fd6fb8aa30b… [5] https://review.trustedfirmware.org/q/I090b888c4acb45c119552fb236343ac10d3c8… [6] https://review.trustedfirmware.org/q/I40deb494ad6d03b9640673044687a4a83c1f7… Alternatively, Change Log is available in the documentation section: https://trustedfirmware-a.readthedocs.io/en/lts-v2.8.46/change-log.html Thanks, TF-A LTS team

1 month, 3 weeks

1
0
0 0

Trusted Firmware-A LTS v2.10.34 Release Announcement

by svc_openci_enginfra＠arm.com

2 months

1
0
0 0

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

by Olivier Deprez

This event has been canceled with a note: "Hi, Cancelling as no topic this week. Thanks & Regards, Olivier. " TF-A Tech Forum Thursday Sep 3, 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 Forum Time: 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… 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 Guests d82620130(a)gmail.com namyoon(a)google.com shaikadnanafrid(a)gmail.com tf-a(a)lists.trustedfirmware.org ~~//~~ Sent by 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

2 months

1
0
0 0

Deprecation notification of Socionext Uniphier, Arm fvp_ve, Broadcom Stingray platforms

by Boyan Karatotev

Hello, During a recent code ownership cleanup we have identified three platforms that lack designated code owners: Socionext Uniphier, Arm fvp_ve, Broadcom Stingray platforms. All three have not had any significant activity for some time now and as such we are going to mark them as deprecated. The patches to do that are here: https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/53842. We will go ahead with them in the next week or so unless we hear any objections. These platforms will not be removed until after the next v2.16 release scheduled for later this year. We will not proceed with removal if code owners are found before then. Thanks, Boyan

2 months, 2 weeks

1
0
0 0

SDEI: SDEI_EVENT_0 trigger dropped while PE masked — by design?

by wtliang785

Hi all, I'd like to ask whether the following behavior of SDEI_EVENT_0 is intended, and whether it's a known limitation of the SDEI + GIC SGI semantics. I've read the code carefully but want to confirm the intent before relying on or working around it. ## Setup - TF-A SDEI, event 0 is a "signalable" private event whose backing interrupt is a Secure SGI (on our platform, SGI 9). - include/services/sdei.h, SDEI_DEFINE_EVENT_0(_intr) -> SDEI_PRIVATE_EVENT(SDEI_EVENT_0, _intr, SDEI_MAPF_SIGNALABLE) - services/std_svc/sdei/sdei_main.c: asserts event 0 must be a Secure SGI and may only carry SIGNALABLE|PRIVATE. ## What I observe in code When the PE is SDEI-masked (client called SDEI_PE_MASK) and the SGI backing event 0 fires, the handler does *not* preserve the trigger: 1. The EL3 FIQ is taken and acked in bl31/ehf.c ehf_el3_interrupt_handler() via plat_ic_acknowledge_interrupt() (reads ICC_IAR — interrupt now Active, its Pending bit consumed). 2. It reaches sdei_intr_handler() (services/std_svc/sdei/sdei_intr_mgmt.c). At L463, state->pe_masked is true, so it calls handle_masked_trigger() and returns 0. 3. handle_masked_trigger() : /* Nothing to do for event 0 */ if (map->ev_num == SDEI_EVENT_0) return; i.e. for event 0 it does none of the "freeze for replay" steps that a normal private event takes : plat_ic_disable_interrupt(intr); plat_ic_set_interrupt_pending(intr); plat_ic_end_of_interrupt(intr_raw); state->pending_enables = true; So while the PE is masked, an event-0 trigger is acknowledged and then silently dropped, with nothing stored for replay on the next SDEI_PE_UNMASK. ## Why I think this happens (and want to confirm) The "freeze for replay" mechanism for normal private events relies on re-asserting Pending via plat_ic_set_interrupt_pending(), because the ack already consumed the Pending bit. But for an SGI this is not permitted — plat/common/plat_gicv3.c: asserts it out: void plat_ic_set_interrupt_pending(unsigned int id) { /* Disallow setting SGIs pending */ assert(id >= MIN_PPI_ID); gicv3_set_interrupt_pending(id, plat_my_core_pos()); } So event 0 (backed by an SGI) cannot have its Pending bit re-asserted in software, which is consistent with the "Nothing to do for event 0" early return. Combined with the level/merge semantics of GIC SGIs (a sender firing the same SGI N times is represented as a single Pending, not a count), this means a masked-PE client can at most learn "an event happened while masked", never how many or which — by design. ## My questions 1. Is dropping an event-0 trigger while the PE is masked the intended behaviour (a consequence of "event 0 is a signalable SGI, counting is not guaranteed"), rather than a bug? The "Nothing to do for event 0" comment reads as deliberate, but I'd like explicit confirmation. 2. Is the recommended mitigation simply to avoid firing event 0 while the PE is masked (buffer on the sender side, deliver after unmask), or to use a normal explicit event for anything requiring precise accounting? Or is there a platform hook intended for this case that I'm missing (e.g. plat_sdei_handle_masked_trigger — though that path is only taken for shared ANY-PE events , not event 0)? 3. Separately (not the focus of this question): on this masked path neither handle_masked_trigger() nor sdei_intr_handler() calls plat_ic_end_of_interrupt() for event 0, and neither the EHF top-level handler nor the runtime_exceptions.S dispatch macro performs a fallback EOI. So the acked SGI appears to be left Active with no EOI on this path. Is there a later EOI for this SGI that I've missed, or is that also expected here? I don't want to conflate this with the "drop" question above; I'm just flagging it. For reference, this is on an in-tree SDEI path; the platform only defines event 0 via SDEI_DEFINE_EVENT_0(PLAT_SDEI_SGI_PRIVATE) and does not modify handle_masked_trigger(). Thanks, Tianliang

2 months, 2 weeks

1
0
0 0

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

by Olivier Deprez

This event has been canceled with a note: "Also cancelling Aug 20th instance as no topic and expected low attendance." TF-A Tech Forum Thursday Aug 20, 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 d82620130(a)gmail.com namyoon(a)google.com shaikadnanafrid(a)gmail.com tf-a(a)lists.trustedfirmware.org ~~//~~ Sent by 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

3 months

1
0
0 0

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

by Olivier Deprez

This event has been canceled with a note: "Hi Cancelling as topic on Aug 6th. Regards, Olivier. " TF-A Tech Forum Thursday Aug 6, 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 d82620130(a)gmail.com namyoon(a)google.com shaikadnanafrid(a)gmail.com tf-a(a)lists.trustedfirmware.org ~~//~~ Sent by 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

3 months

1
0
0 0

Lava Lab downtime tomorrow 06/06/2026

by Ben Copeland

Hello all, Please be aware that tomorrow, 06/06/2026, the Lava Lab will be down due to a UPS replacement. The time will be 13:00 to 17:00 (UTC+1). Regards Ben

3 months

1
1
0 0

Trusted Firmware-A LTS v2.14.6 Release Announcement

by svc_openci_enginfra＠arm.com

Hello, Trusted Firmware-A LTS version 2.14.6 is now available. This release contains the following patches: 3bd0e9acb feat(mt8196): add CPU errata workarounds [1] 2c2699824 fix(versal2): enable A78AE errata workarounds [2] 7a5b2b3a0 fix(versal-net): enable A78AE errata workarounds [3] c731d419c fix(xilinx): pass security_flag to eemi_psci_debugfs_handler [4] [1] https://review.trustedfirmware.org/q/Ia1a89c462c2ce600302c54eb5c289ed9501b4… [2] https://review.trustedfirmware.org/q/I598ea03c800ff685d57f97fdc519bda3c53a1… [3] https://review.trustedfirmware.org/q/Id7a0f53595eba6140e131dab529d75cdafa35… [4] https://review.trustedfirmware.org/q/Ie8b5fc95ae83a98d8d9d58562be8407bd4468… Alternatively, Change Log is available in the documentation section: https://trustedfirmware-a.readthedocs.io/en/lts-v2.14.6/change-log.html Thanks, TF-A LTS team

3 months, 1 week

1
0
0 0

Trusted Firmware-A LTS v2.12.14 Release Announcement

by svc_openci_enginfra＠arm.com

Hello, Trusted Firmware-A LTS version 2.12.14 is now available. This release contains the following patches: e6f0750c7 fix(xilinx): pass security_flag to eemi_psci_debugfs_handler [1] 80f4f28b8 fix(versal2): enable A78AE errata workarounds [2] 50224b40e fix(versal-net): enable A78AE errata workarounds [3] 327504e3d fix(nxp): move PLAT_FUSE_FIP_* to plat_default_def [4] d3fc9d67d fix(stm32mp1): force soft float ABI and disable NEON [5] 78674e3e9 docs: fill TFV advisory titles [6] bfd109e39 fix(nxp): imx_trdc.h header guard [7] [1] https://review.trustedfirmware.org/q/Ie8b5fc95ae83a98d8d9d58562be8407bd4468… [2] https://review.trustedfirmware.org/q/I598ea03c800ff685d57f97fdc519bda3c53a1… [3] https://review.trustedfirmware.org/q/Id7a0f53595eba6140e131dab529d75cdafa35… [4] https://review.trustedfirmware.org/q/I6777e342a439d484ea52ea851beb15afb2dc6… [5] https://review.trustedfirmware.org/q/Ic9a7da8ec5b2f019a1cf61c82dc058469d1f2… [6] https://review.trustedfirmware.org/q/I17705b3a2ca2a04ee5698fb86b0d2524033e3… [7] https://review.trustedfirmware.org/q/I4767dc4d1c26ebe95d417be724f5cb848f54a… Alternatively, Change Log is available in the documentation section: https://trustedfirmware-a.readthedocs.io/en/lts-v2.12.14/change-log.html Thanks, TF-A LTS team

3 months, 1 week

1
0
0 0

Trusted Firmware-A LTS v2.8.45 Release Announcement

by svc_openci_enginfra＠arm.com

3 months, 1 week

1
0
0 0

Trusted Firmware-A LTS v2.10.33 Release Announcement

by svc_openci_enginfra＠arm.com

Hello, Trusted Firmware-A LTS version 2.10.33 is now available. This release contains the following patches: 0afda0393 fix(xilinx): pass security_flag to eemi_psci_debugfs_handler [1] [1] https://review.trustedfirmware.org/q/Ie8b5fc95ae83a98d8d9d58562be8407bd4468… Alternatively, Change Log is available in the documentation section: https://trustedfirmware-a.readthedocs.io/en/lts-v2.10.33/change-log.html Thanks, TF-A LTS team

3 months, 1 week

1
0
0 0

[TFA][RFC] Relaxing FWU metadata validation to support variable-size metadata

by Maxime MERE

Hi all, I'd like some early feedback on an approach before writing it up as patches for Gerrit review. It would relax the generic FWU metadata sanity checks in fwu.c, and let us remove some STM32MP-specific code that would become dead as a result. Motivation On STM32MP platforms we need to support boards that can be flashed either with a GPT/block-device layout (SD/eMMC) or with a raw/MTD layout (NOR/NAND), while reusing the same U-Boot binary/configuration across both. The two layouts don't need to describe the same firmware image set in their FWU metadata: the block-device variant uses an A/B redundant layout covering FIP + BootFS + RootFS (3 images per bank), while the raw-storage variant only ever needs a single FIP per bank (no GPT, no room for a generic BootFS/RootFS A/B scheme). This was highlighted by a 4-patch series by Dario already in TF-A tree ("feat(st): add extended bootloader GUID" / "feat(st): add Linux data partition GUID" / "feat(st): add STM32MP_PSA_FWU_AB_SUPPORT build flag" / "feat(st): enable A/B redundancy support"), which introduces exactly that 3-image A/B layout for GPT-based STM32MP boards by raising NR_OF_IMAGES_IN_FW_BANK to 3. The problem: fwu_metadata_sanity_check() currently requires an exact match between the metadata-declared num_images/size and the platform's compiled configuration, and computes the CRC over sizeof(struct fwu_metadata) instead of the metadata-declared metadata_size. This forces every board variant sharing a single TF-A build to describe exactly the same image set/size in its FWU metadata, which isn't what the spec intends. What the spec says (DEN0118 FWU-1.0 A EAC1 see https://developer.arm.com/documentation/den0118/latest/) Table A3.2 explicitly introduces metadata_size in v2 as "The size in bytes of the complete metadata structure", and defines the CRC as computed over the declared size, not a fixed maximum. Table A3.3 defines num_images as "The number of entries in the img_entry array" (img_entry[num_images]), again variable by design. The spec also explicitly allows #banks < 4, but in the current C struct layout num_banks also determines the byte stride of each img_entry (bank_info_entry_size * num_banks), so relaxing it would require decoding img_entry[] with a runtime-computed stride instead of the fixed compile-time layout so I'd rather keep that out of scope for now. What I'm proposing In the common FWU driver (fwu.c), replace the equality checks with bounds that only reject metadata a platform genuinely cannot handle: - Compute the CRC over metadata.metadata_size instead of sizeof(struct fwu_metadata), matching the spec. - Accept num_images <= NR_OF_IMAGES_IN_FW_BANK instead of requiring strict equality. - Bound metadata_size itself between FWU_FW_STORE_DESC_OFFSET (0x20, the minimum valid v2 size) and sizeof(struct fwu_metadata), to reject malformed metadata and avoid any out-of-bounds read. - Keep num_banks as an exact match against NR_OF_FW_BANKS, for the layout reason above. On the STM32MP side, plat_fwu_set_images_source() currently iterates every image entry described by the metadata and tries to resolve a storage offset for each of them. On raw storage devices (NOR/NAND) only two hardcoded bank GUIDs are known, so any entry other than the FIP (e.g. BootFS/RootFS added by STM32MP_PSA_FWU_AB_SUPPORT) causes a panic, even though BL2 never actually loads BootFS/RootFS itself (only U-Boot/Linux/the update agent do). I'd change it to search explicitly for the FIP image type GUID and resolve only that entry, using metadata.fw_desc.num_images (now safely bounded by point 1) as the search bound instead of the compiled NR_OF_IMAGES_IN_FW_BANK. The function then becomes agnostic of how many, or which, other image types a given metadata instance may describe. As a direct consequence of point 2, the per-image IO policies, image IDs and GUID definitions (XBOOTLDR_GUID, LINUX_FILE_SYSTEM_DATA_GUID) added for BootFS/RootFS become dead code from BL2's point of view (they were only needed so plat_fwu_set_images_source() could resolve those entries). I'd remove them, while keeping the STM32_EXTRA_PARTS accounting fix (load_partition_table() truncates the parsed GPT to a fixed-size list, so the extra bootfs-a/b, rootfs-a/b, vendorfs and u-boot-env partitions still physically present on an A/B board must still be accounted for, even though BL2 no longer resolves them individually). Validation Tested on hardware: - A TF-A build configured for the 3-image A/B layout (NR_OF_IMAGES_IN_FW_BANK = 3, STM32MP_PSA_FWU_AB_SUPPORT=1) booting successfully off FWU metadata that only declares a single image entry (num_images = 1), confirming a platform built for the larger capacity can consume metadata that uses a smaller subset. - The existing single-image configuration (NR_OF_IMAGES_IN_FW_BANK = 1) still boots correctly with unchanged, exact-match metadata, confirming no regression on the base FWU flow. Questions for the list - Is the community comfortable relaxing this check in common code (fwu.c), given it affects every platform enabling PSA_FWU_METADATA_FW_STORE_DESC? - Is anyone aware of a downstream user relying on the current exact-match behaviour that this change would affect? If this sounds reasonable I'll post the actual patches to Gerrit for review. Thanks, Maxime

3 months, 1 week

3
3
0 0

Trusted Firmware-A LTS v2.12.13 Release Announcement

by svc_openci_enginfra＠arm.com

3 months, 2 weeks

1
0
0 0

Trusted Firmware-A LTS v2.10.32 Release Announcement

by svc_openci_enginfra＠arm.com

3 months, 2 weeks

1
0
0 0

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

by Olivier Deprez

This event has been canceled with a note: "Hi, Cancelling as no topic planned this week. Regards, Olivier. " TF-A Tech Forum Thursday Jul 23, 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 d82620130(a)gmail.com namyoon(a)google.com shaikadnanafrid(a)gmail.com 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

3 months, 2 weeks

1
0
0 0

Trusted Firmware-A LTS v2.8.44 Release Announcement

by svc_openci_enginfra＠arm.com

Hello, Trusted Firmware-A LTS version 2.8.44 is now available. This release contains the following patches: 8eda1543f fix(a8k): declare amb_memory_map as an array [1] bab6976e6 fix(a8k): mv_ddr path may not be a git repo [2] b8c8b3aba fix(marvell): provide a default compile target [3] 970b6d9e2 feat(fvp): give bootargs on all configs [4] c7e250265 feat(fvp): give bootargs on all configs [5] c6b6e1c81 feat(fvp): define ns memory in the SPMC manifest [6] 950ad8d8e fix(spm): add device-regions used in tf-a-tests [7] 5d6ba544e fix(spm): change the SMMUv3TestEngine being used [8] c037569fc fix(ff-a): add NS memory node to fvp_spmc_optee_sp manifest [9] 787e7db3e feat(fvp): set defaults for build commandline [10] c214e2f5a feat(common): add support for kernel DT handoff convention [11] dcde3d3be feat(fvp): enable kernel dt convention [12] 989186231 feat(arm): unify Linux kernel as BL33 handling [13] 4caaf6bb2 fix(arm): increase reserved DRAM1 mem for NS images [14] a9f43bb50 fix(armada): mv_ddr path may not be a git repo [15] 96b851128 feat(arm): add initrd props to dtb at build time [16] 63e321558 feat(build): add Mbed TLS submodule [17] ae9ff807e feat(mbedtls): update mbedTLS to version 3.6.6 [18] [1] https://review.trustedfirmware.org/q/I5608be6401bfbc1291ded85a8fbce8abe169d… [2] https://review.trustedfirmware.org/q/Ieaff6281785993873c7cb26ddc1d90d0896ad… [3] https://review.trustedfirmware.org/q/Id93d71876a81e442e6612eae2b0e7cb12e0fd… [4] https://review.trustedfirmware.org/q/I4e7f582862ba9a0a96c0d6de10d021eed5174… [5] https://review.trustedfirmware.org/q/I78874344b5972ae3ff136da5a8f119d376d53… [6] https://review.trustedfirmware.org/q/Iad03eb138a57068fbb18c53141bdf6bf9c171… [7] https://review.trustedfirmware.org/q/I47376e67c700705d12338d7078292618a15d5… [8] https://review.trustedfirmware.org/q/I6f7f235d022090189782381bc88e67de64c11… [9] https://review.trustedfirmware.org/q/I9daf3182e0dcb73d2bf5a5baffb1b4b78c724… [10] https://review.trustedfirmware.org/q/I0396b597485e163b43f7c6677c04fcc08db55… [11] https://review.trustedfirmware.org/q/I6bd7154fe07cb2e16e25c058f7cf862f9ae00… [12] https://review.trustedfirmware.org/q/Ieea8cfe68104b82038b9311613abf13afe7b4… [13] https://review.trustedfirmware.org/q/Ib668dbb1de9d42cf41c0b0ee9a316f0548917… [14] https://review.trustedfirmware.org/q/Ifffdda4623ec7930e4c830a6a222933807d09… [15] https://review.trustedfirmware.org/q/I7b5c2367d4ad8ddb6a2ff0b20a5206d972e42… [16] https://review.trustedfirmware.org/q/Ief8de5f00c453509bcc6e978e0a95d768f1f5… [17] https://review.trustedfirmware.org/q/Iad777e77936d1c373065f17fe5c4aadc45e56… [18] https://review.trustedfirmware.org/q/I9f90eecfbce203a89c61e864ef3f85677efad… Alternatively, Change Log is available in the documentation section: https://trustedfirmware-a.readthedocs.io/en/lts-v2.8.44/change-log.html Thanks, TF-A LTS team

3 months, 3 weeks

1
0
0 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

TF-A