Page MenuHomePhabricator
Feed All Stories

Fri, Sep 30

vwadekar edited the content of Long-term support (LTS) proposal.
Fri, Sep 30, 11:40 AM
vwadekar edited the content of Long-term support (LTS) proposal.
Fri, Sep 30, 11:39 AM

Tue, Sep 27

gyuri-szing updated subscribers of T993: Premature, forced OpenSSL 3.0 API upgrade..

it seems there are two existing workarounds related to OpenSSL3 available in different downstream projects.

Tue, Sep 27, 9:18 AM · TF-A Question, Trusted Firmware A
Luoject assigned T1003: TF-A: RPi4 fails to boot secondary core at second time by PSCI cpu_on to Andre-ARM.

Hi Andre-ARM, to fix the problem, here's the pull request: https://github.com/ARM-software/arm-trusted-firmware/pull/1988

Tue, Sep 27, 7:44 AM · Trusted Firmware A, TF-A Bug
Luoject added a comment to T1003: TF-A: RPi4 fails to boot secondary core at second time by PSCI cpu_on.

Hi,
thanks for the info, I will have a look at this, though probably only later this week.
As for rebuilding: I assume you are using the firmware drops from the pftf github?
This is deeply hidden in the EDK2 build system, but it will effectively use a precompiled version of bl31.bin checked into the edk2-non-osi.git repository. This will be placed into the first 128KB of RPI_EFI.fd file, filled up with 0xff.
So to replace just bl31.bin, you simply overwrite the first part of that file, with your compiled version.
To get bl31.bin from source, you just need an aarch64 (cross-)compiler, then:
$ CROSS_COMPILE=aarch64-linux-gnu- make PLAT=rpi4 DEBUG=0
This should be described in docs/plat/rpi4.rst. If you find something missing, let me know, or even better: send a patch ;-)

Tue, Sep 27, 5:18 AM · Trusted Firmware A, TF-A Bug

Mon, Sep 26

vwadekar edited the content of Long-term support (LTS) proposal.
Mon, Sep 26, 9:05 PM
vwadekar edited the content of Long-term support (LTS) proposal.
Mon, Sep 26, 9:03 PM
Andre-ARM added a comment to T1003: TF-A: RPi4 fails to boot secondary core at second time by PSCI cpu_on.

Hi,
thanks for the info, I will have a look at this, though probably only later this week.
As for rebuilding: I assume you are using the firmware drops from the pftf github?
This is deeply hidden in the EDK2 build system, but it will effectively use a precompiled version of bl31.bin checked into the edk2-non-osi.git repository. This will be placed into the first 128KB of RPI_EFI.fd file, filled up with 0xff.
So to replace just bl31.bin, you simply overwrite the first part of that file, with your compiled version.
To get bl31.bin from source, you just need an aarch64 (cross-)compiler, then:
$ CROSS_COMPILE=aarch64-linux-gnu- make PLAT=rpi4 DEBUG=0
This should be described in docs/plat/rpi4.rst. If you find something missing, let me know, or even better: send a patch ;-)

Mon, Sep 26, 1:18 PM · Trusted Firmware A, TF-A Bug
Luoject added a comment to T1003: TF-A: RPi4 fails to boot secondary core at second time by PSCI cpu_on.

So that's a lot of details (thanks for that!), but what is the actual problem? That secondaries cannot be taken offline? Or that they don't came back online? And did that work before the commit you mentioned?

Mon, Sep 26, 12:09 PM · Trusted Firmware A, TF-A Bug
Andre-ARM added a comment to T1003: TF-A: RPi4 fails to boot secondary core at second time by PSCI cpu_on.

So that's a lot of details (thanks for that!), but what is the actual problem? That secondaries cannot be taken offline? Or that they don't came back online? And did that work before the commit you mentioned?

Mon, Sep 26, 9:55 AM · Trusted Firmware A, TF-A Bug
Luoject updated the task description for T1003: TF-A: RPi4 fails to boot secondary core at second time by PSCI cpu_on.
Mon, Sep 26, 7:42 AM · Trusted Firmware A, TF-A Bug

Sun, Sep 25

felixsinger added a comment to T996: Compiling bl31.elf with binutils 2.39 warns/fails with “ LOAD segment with RWX permissions”.

I can confirm this occurs with binutils 2.39. We (coreboot) are trying to update binutils from our toolchain and we are about to adjust our build system. --no-warn-rwx-segment fixes the issue. https://review.coreboot.org/c/coreboot/+/66920

Sun, Sep 25, 4:40 PM · Trusted Firmware A

Sat, Sep 24

joannafarley-arm updated subscribers of T1003: TF-A: RPi4 fails to boot secondary core at second time by PSCI cpu_on.

Pinging @Andre-ARM RPi4 platform code owner for comment.

Sat, Sep 24, 3:23 PM · Trusted Firmware A, TF-A Bug
Luoject added a project to T1003: TF-A: RPi4 fails to boot secondary core at second time by PSCI cpu_on: Trusted Firmware A.
Sat, Sep 24, 11:02 AM · Trusted Firmware A, TF-A Bug
Luoject created T1003: TF-A: RPi4 fails to boot secondary core at second time by PSCI cpu_on.
Sat, Sep 24, 11:01 AM · Trusted Firmware A, TF-A Bug

Thu, Sep 22

zandrey added a comment to T1000: imx8m does not start after EHF with S-EL2 SPMC change.

Hello Olivier,

Thu, Sep 22, 1:05 PM · Trusted Firmware A, TF-A Bug
odeprez added a comment to T1000: imx8m does not start after EHF with S-EL2 SPMC change.

Thanks for your reply. Looks like there is a fix under works:

Thu, Sep 22, 11:22 AM · Trusted Firmware A, TF-A Bug
mirschkyn added a comment to T996: Compiling bl31.elf with binutils 2.39 warns/fails with “ LOAD segment with RWX permissions”.

Adding that the linking warns about both rwx-sections and execstack for bl2 too.
So both are needed or the linking needs to be fixed.
I think the no-warn flags are only available to newer tools, so defaulting to them will probably break things.

Thu, Sep 22, 10:50 AM · Trusted Firmware A

Tue, Sep 20

odeprez created T1002: Revisit hypervisor page tables defragmentation.
Tue, Sep 20, 8:07 AM · Hafnium

Mon, Sep 19

eriders updated eriders.
Mon, Sep 19, 4:37 PM

Sat, Sep 17

zandrey added a comment to T1000: imx8m does not start after EHF with S-EL2 SPMC change.

Hello Olivier,

Sat, Sep 17, 7:34 PM · Trusted Firmware A, TF-A Bug

Tue, Sep 13

madhukar-Arm updated the task description for T1001: Improvements to secure interrupt handling, partition runtime models and scheduling modes in Hafnium.
Tue, Sep 13, 5:39 PM · Hafnium
madhukar-Arm updated the task description for T1001: Improvements to secure interrupt handling, partition runtime models and scheduling modes in Hafnium.
Tue, Sep 13, 5:39 PM · Hafnium
madhukar-Arm updated the task description for T1001: Improvements to secure interrupt handling, partition runtime models and scheduling modes in Hafnium.
Tue, Sep 13, 5:37 PM · Hafnium
madhukar-Arm updated the task description for T1001: Improvements to secure interrupt handling, partition runtime models and scheduling modes in Hafnium.
Tue, Sep 13, 5:37 PM · Hafnium
madhukar-Arm updated the task description for T1001: Improvements to secure interrupt handling, partition runtime models and scheduling modes in Hafnium.
Tue, Sep 13, 5:36 PM · Hafnium
madhukar-Arm triaged T1001: Improvements to secure interrupt handling, partition runtime models and scheduling modes in Hafnium as Normal priority.
Tue, Sep 13, 5:34 PM · Hafnium
odeprez added a comment to T1000: imx8m does not start after EHF with S-EL2 SPMC change.

Hi,
From the logs I understand BL31 is started by U-Boot SPL rather than TF-A's BL1/BL2, correct?
Would it be possible to gather more verbose logs (build with DEBUG=1 LOG_LEVEL=50) ?
Can you share the TF-A command line used to build this platform?
In particular what's the state of EL3_EXCEPTION_HANDLING, SPD, SPMD_SPM_AT_SEL2 toggles?
Thanks, Olivier.

Tue, Sep 13, 7:54 AM · Trusted Firmware A, TF-A Bug

Sun, Sep 11

joannafarley-arm updated subscribers of T1000: imx8m does not start after EHF with S-EL2 SPMC change.

Ping @raghuncstate for comment https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git/commit/?id=7c2fe62f1347bb94d82e9fdd3bc5eaebedaf0bc7

Sun, Sep 11, 10:20 AM · Trusted Firmware A, TF-A Bug

Sat, Sep 10

zandrey added projects to T1000: imx8m does not start after EHF with S-EL2 SPMC change: TF-A Bug, Trusted Firmware A.
Sat, Sep 10, 8:21 PM · Trusted Firmware A, TF-A Bug

Fri, Sep 9

zandrey created T1000: imx8m does not start after EHF with S-EL2 SPMC change.
Fri, Sep 9, 2:58 PM · Trusted Firmware A, TF-A Bug

Thu, Sep 8

joannafarley-arm added a comment to T996: Compiling bl31.elf with binutils 2.39 warns/fails with “ LOAD segment with RWX permissions”.

Hey Chris, I may have raised the bug wrong we are tracking internally as its binutils-2.39, sorry!

Thu, Sep 8, 4:33 PM · Trusted Firmware A
CJKay added a comment to T996: Compiling bl31.elf with binutils 2.39 warns/fails with “ LOAD segment with RWX permissions”.

Hi Heitbaum, could you tell me which toolchain you're using to build TF-A? The latest Arm GNU AArch64 toolchain is 11.3.Rel1, which packages binutils-2.38 and therefore compiles successfully, so I'm currently unable to reproduce this error.

Thu, Sep 8, 3:53 PM · Trusted Firmware A

Aug 29 2022

hramrach renamed T999: TF-A does not build with GCC 7 for some platforms from TF-A doe not build with GCC 7 for some platforms to TF-A does not build with GCC 7 for some platforms.
Aug 29 2022, 12:46 PM · TF-A Bug
hramrach added a comment to T999: TF-A does not build with GCC 7 for some platforms.

Aug 29 2022, 12:45 PM · TF-A Bug
hramrach created T999: TF-A does not build with GCC 7 for some platforms.
Aug 29 2022, 12:44 PM · TF-A Bug

Aug 19 2022

joannafarley-arm closed T998: dtc warns when compiling TF-A with FVP_HW_CONFIG_DTS=fdts/fvp-base-gicv3-psci-1t.dts as Resolved.
Aug 19 2022, 1:16 PM · Trusted Firmware A
nadlertz added a comment to T998: dtc warns when compiling TF-A with FVP_HW_CONFIG_DTS=fdts/fvp-base-gicv3-psci-1t.dts.

I see. Thanks for the replies. Feel free to close this task then.

Aug 19 2022, 11:34 AM · Trusted Firmware A
joannafarley-arm added a comment to T998: dtc warns when compiling TF-A with FVP_HW_CONFIG_DTS=fdts/fvp-base-gicv3-psci-1t.dts.

Regarding this web page reporting system its mainly now being used for Bug reporting. There is now a TF-A mailing list https://lists.trustedfirmware.org/mailman3/lists/tf-a.lists.trustedfirmware.org/ where many more people can help with questions.

Aug 19 2022, 11:21 AM · Trusted Firmware A
Andre-ARM added a comment to T998: dtc warns when compiling TF-A with FVP_HW_CONFIG_DTS=fdts/fvp-base-gicv3-psci-1t.dts.

Yes, this is a known issue. The DTs for the base FVP model were once imported from the Linux tree, but haven't been updated since. Meanwhile both DTC and the DT schema compliance tooling in the kernel tree got stricter, so the old files trigger warnings now.
One could go ahead and just fix each of those warnings, but I am actually working on rearranging the FVP DT files, so we can sync them from the kernel tree. That should fix those messages automatically.

Aug 19 2022, 11:03 AM · Trusted Firmware A

Aug 17 2022

nadlertz updated the task description for T998: dtc warns when compiling TF-A with FVP_HW_CONFIG_DTS=fdts/fvp-base-gicv3-psci-1t.dts.
Aug 17 2022, 7:44 AM · Trusted Firmware A
nadlertz added a comment to T998: dtc warns when compiling TF-A with FVP_HW_CONFIG_DTS=fdts/fvp-base-gicv3-psci-1t.dts.

I tried to follow the guidelines on https://github.com/ARM-software/tf-issues but I can't find where to add the "question" label. Sorry about this.

Aug 17 2022, 7:38 AM · Trusted Firmware A
nadlertz triaged T998: dtc warns when compiling TF-A with FVP_HW_CONFIG_DTS=fdts/fvp-base-gicv3-psci-1t.dts as Low priority.
Aug 17 2022, 7:35 AM · Trusted Firmware A

Aug 15 2022

pfalcon created T997: MISRA: Bare usage of __builtin_offsetof() should be avoided.
Aug 15 2022, 8:08 PM
joannafarley-arm added a comment to T996: Compiling bl31.elf with binutils 2.39 warns/fails with “ LOAD segment with RWX permissions”.

Hi Heitaum, Thanks for reporting this.

Aug 15 2022, 9:18 AM · Trusted Firmware A

Aug 10 2022

heitbaum created T996: Compiling bl31.elf with binutils 2.39 warns/fails with “ LOAD segment with RWX permissions”.
Aug 10 2022, 12:18 PM · Trusted Firmware A
joannafarley-arm added a comment to T989: Support SVE in non-secure world with CTX_INCLUDE_FPREGS=1.

Sure, people are of course free to do what they want downstream. Especially as a temporary measure if this is ultimately needed to be upstreamed with fuller discussion once other stakeholders are available to facilitate that.

Aug 10 2022, 8:37 AM · Trusted Firmware A

Aug 9 2022

okash added a comment to T989: Support SVE in non-secure world with CTX_INCLUDE_FPREGS=1.

Thanks Joanna for letting know. This is actually blocking development so I'm thinking we go ahead with a local change that we think will be best and then we can discuss that change when Soby is back. What do you think?

Aug 9 2022, 7:23 PM · Trusted Firmware A
cringti edited the content of Proof Of Concepts.
Aug 9 2022, 4:55 PM
pfalcon created T995: TF-A: Piping source code to $CC complicates usage of static analysis tools.
Aug 9 2022, 3:00 PM

Aug 8 2022

joannafarley-arm added a comment to T989: Support SVE in non-secure world with CTX_INCLUDE_FPREGS=1.

Soby, himself is out until towards end of August. Maybe wait now until Beginning of Septif this is not urgent?

Aug 8 2022, 8:30 PM · Trusted Firmware A
okash added a comment to T989: Support SVE in non-secure world with CTX_INCLUDE_FPREGS=1.

Apologies, holiday delays on our side too :)

Aug 8 2022, 6:22 PM · Trusted Firmware A

Jul 29 2022

AntonioSanta triaged T994: cannot read beyond 4Gbyte space from eMMC, NXP's sd_mmc driver as Normal priority.
Jul 29 2022, 2:09 PM · TF-A Bug

Jul 19 2022

tenkaisakura7 updated tenkaisakura7.
Jul 19 2022, 6:36 AM

Jul 15 2022

balintdobszay published a new version of OP-TEE SPMC status v3.18.
Jul 15 2022, 1:30 PM · Trusted Services
balintdobszay renamed OP-TEE SPMC status v3.18 from OP-TEE SPMC status v3.17 to OP-TEE SPMC status v3.18.
Jul 15 2022, 1:30 PM · Trusted Services
balintdobszay renamed OP-TEE SPMC status v3.18 from OP-TEE SPMC status v3.17 to OP-TEE SPMC status v3.18.
Jul 15 2022, 1:22 PM · Trusted Services
balintdobszay renamed OP-TEE SPMC status v3.18 from OP-TEE SPMC status v3.17 to OP-TEE SPMC status v3.18.
Jul 15 2022, 1:01 PM · Trusted Services
balintdobszay renamed OP-TEE SPMC status v3.18 from OP-TEE SPMC status v3.17 to OP-TEE SPMC status v3.18.
Jul 15 2022, 12:58 PM · Trusted Services
balintdobszay renamed OP-TEE SPMC status v3.18 from OP-TEE SPMC status v3.17 to OP-TEE SPMC status v3.18.
Jul 15 2022, 12:45 PM · Trusted Services

Jul 11 2022

skysuryakumar updated skysuryakumar.
Jul 11 2022, 4:40 PM

Jul 6 2022

michele654 added a comment to Mbed TLS Security Center.

The link to the security advisories at the old Mbed TLS website redirects now to the new trustedfirmware.org website, so there is no place to see the security advisories.

Jul 6 2022, 12:35 PM

Jul 5 2022

shebuk edited the content of Roadmap.
Jul 5 2022, 1:00 PM
shebuk edited the content of Roadmap.
Jul 5 2022, 12:38 PM
shebuk edited the content of Roadmap.
Jul 5 2022, 10:09 AM

Jul 4 2022

balintdobszay renamed OP-TEE SPMC status v3.18 from OP-TEE SPMC status v3.17 to OP-TEE SPMC status v3.18.
Jul 4 2022, 1:43 PM · Trusted Services
balintdobszay renamed OP-TEE SPMC status v3.18 from OP-TEE SPMC status v3.17 to OP-TEE SPMC status v3.18.
Jul 4 2022, 1:39 PM · Trusted Services
balintdobszay renamed OP-TEE SPMC status v3.18 from OP-TEE SPMC status v3.17 to OP-TEE SPMC status v3.18.
Jul 4 2022, 1:38 PM · Trusted Services
balintdobszay renamed OP-TEE SPMC status v3.18 from OP-TEE SPMC status v3.17 to OP-TEE SPMC status v3.18.
Jul 4 2022, 1:37 PM · Trusted Services
balintdobszay renamed OP-TEE SPMC status v3.18 from OP-TEE SPMC status v3.17 to OP-TEE SPMC status v3.18.
Jul 4 2022, 12:08 PM · Trusted Services

Jul 1 2022

ManishVB-Arm added a comment to T993: Premature, forced OpenSSL 3.0 API upgrade..

HI Mirschkym,

Jul 1 2022, 12:52 PM · TF-A Question, Trusted Firmware A
dohoangvan added a watcher for Hafnium: dohoangvan.
Jul 1 2022, 8:12 AM

Jun 29 2022

joannafarley-arm added a comment to T993: Premature, forced OpenSSL 3.0 API upgrade..

Hi Mirschkym, just acknowledging your ticket. We are working on a response on how best to address your issue.

Jun 29 2022, 2:33 PM · TF-A Question, Trusted Firmware A

Jun 28 2022

pmanish87 added a watcher for Trusted Firmware A: pmanish87.
Jun 28 2022, 11:47 AM
ManishVB-Arm added a watcher for Trusted Firmware A: ManishVB-Arm.
Jun 28 2022, 11:46 AM
adeaarm updated the task description for T958: Create a JSON description of the driver module.
Jun 28 2022, 8:44 AM · Restricted Project
mirschkyn added a project to T993: Premature, forced OpenSSL 3.0 API upgrade.: TF-A Question.
Jun 28 2022, 7:34 AM · TF-A Question, Trusted Firmware A
mirschkyn created T993: Premature, forced OpenSSL 3.0 API upgrade..
Jun 28 2022, 7:33 AM · TF-A Question, Trusted Firmware A

Jun 22 2022

soby-mathew added a comment to T989: Support SVE in non-secure world with CTX_INCLUDE_FPREGS=1.

Hi Okash,
Olivier is on holiday and once he is back next week, we can arrange something to discuss.

Jun 22 2022, 9:02 AM · Trusted Firmware A

Jun 20 2022

okash added a comment to T989: Support SVE in non-secure world with CTX_INCLUDE_FPREGS=1.

Thanks. It seems like we are converging. Would it make sense to set up a meeting to thrash out details? Any time this week will be preferable. Let me know what works for you. Arve and Peter are in Pacific time zone. Rest of us are based in UK I guess?

Jun 20 2022, 5:44 PM · Trusted Firmware A
RajHorizon added a watcher for Hafnium: RajHorizon.
Jun 20 2022, 9:03 AM

Jun 18 2022

ramakrishnanew updated ramakrishnanew.
Jun 18 2022, 12:52 PM

Jun 13 2022

soby-mathew added a comment to T989: Support SVE in non-secure world with CTX_INCLUDE_FPREGS=1.

That is not what I meant. The NS SVE/FP access trap is needed to avoid saving and restoring the state when the SVE/FP registers are actively used by the secure world.

Jun 13 2022, 10:27 AM · Trusted Firmware A

Jun 10 2022

arve-android added a comment to T989: Support SVE in non-secure world with CTX_INCLUDE_FPREGS=1.

Hi Arve

S-EL2 cannot lazily save and restore the non secure register state though since it cannot trap accesses by the normal world. I have not thought much about how to optimize a lazy save and restore mechanism where a lower exception level also uses lazy save and restore, but I don't think the secure world is fundamentally different from the normal world here.

S-EL2 does not need to trap access by Normal world to do a lazy save and restore. The sequence that I have in mind would be something like below:

  1. EL3 switches to the S-EL2 on receipt of a FF-A call from Non Secure. SPM schedules the right S-EL1 partition with the SVE and FP trap enabled. Note that the NS FPU/SVE is still present in the registers at this point in time.
  2. S-EL1 SP now tries to access FP/SVE and takes a trap to SPM in S-EL2. SPM now saves the NS FPU/SVE context and restores the S-EL1 SP FP/SVE context and disables the trap. It reenters the S-EL1 partition.
  3. The partition is now able to use SVE/FP and completes its work. Returns back to SPM.
  4. SPM now saves the SP FP/SVE context and restores the NS SVE/FP context. Return back to NS caller via EL3.

As can be seen, The SPM does not need to trap NS SVE/FP accesses.

That is not what I meant. The NS SVE/FP access trap is needed to avoid saving and restoring the state when the SVE/FP registers are actively used by the secure world, but not by the normal world. In the sequence you describe the lazy save and restore is only lazy when the secure world does not use the SVE/FP registers.

Jun 10 2022, 9:43 PM · Trusted Firmware A
odeprez added a comment to T989: Support SVE in non-secure world with CTX_INCLUDE_FPREGS=1.

Hi,

on systems that don't support S-EL2, SPMC functionality mostly, if not all, resides in EL3

This is an implementation choice. E.g. OP-TEE implements an S-EL1 SPMC without needing SPMC logic at EL3 (beyond the SPMD as FF-A relayer).
If you consider the EL3 FF-A SPMC just recently added, yes most of the SPMC logic resides at EL3.

Jun 10 2022, 6:33 AM · Trusted Firmware A

Jun 9 2022

okash added a comment to T989: Support SVE in non-secure world with CTX_INCLUDE_FPREGS=1.

Hey Soby and Olivier, on systems that don't support S-EL2, SPMC functionality mostly, if not all, resides in EL3 right? Going by that convention, would it make sense to have SVE save and restore in EL3? We can make it part of SPMC code in EL3. For additional space we can make use of DDR carveout as Soby mentioned above. Moreover, if we make that context save and restore part enablement configurable at compile time, then platform can choose whether they want the functionality. Would it then be acceptable?

Jun 9 2022, 10:25 PM · Trusted Firmware A

May 24 2022

odeprez added a comment to T989: Support SVE in non-secure world with CTX_INCLUDE_FPREGS=1.

Hi,
Today SEL2 unconditionally saves/restores FP/SIMD/SVE NS context on any SEL2 entry/exit.
I believe it could be optimized the way Soby is describing it by bullets 1,2,3,4.
It is worth noting that when SEL2 is not present (e.g. using the EL3 FF-A SPMC and a SEL1 TOS), the same lazy NS and TA contexts save/restore mechanism can be used by a SEL1 TOS and EL3 doesn't have to bother.

May 24 2022, 8:53 AM · Trusted Firmware A
soby-mathew added a comment to T989: Support SVE in non-secure world with CTX_INCLUDE_FPREGS=1.

Hi Arve

May 24 2022, 8:39 AM · Trusted Firmware A

May 23 2022

arve-android added a comment to T989: Support SVE in non-secure world with CTX_INCLUDE_FPREGS=1.

When you have a S-EL2 based system with possibly multiple S-EL1 partitions, it would be complex to implement a scheme where in EL3 will restore the right S-EL1 context on taking a trap during lazy save mechanism. In such systems, it is easier for S-EL2 to implement such a scheme since it is the manager for S-EL1 contexts.

S-EL2 cannot lazily save and restore the non secure register state though since it cannot trap accesses by the normal world. I have not thought much about how to optimize a lazy save and restore mechanism where a lower exception level also uses lazy save and restore, but I don't think the secure world is fundamentally different from the normal world here. You can have lazy save and restore in NS-EL1, NS-EL2, S-EL1, S-EL2 and EL3. I think it is worthwhile to see how this can be optimized to avoid saving and restoring register states that will not be used, but I would like to see a solution that does not leak data between execution environments that are supposed to be isolated.

May 23 2022, 8:05 PM · Trusted Firmware A

May 20 2022

bipinravi-arm added a comment to T991: Compiling atf for iMX8 using gcc-12..1 fails.

TF-A works on a 6 month release cadence and we typically update the gcc toolchain to the latest released version along with the TF-A release. gcc versions we use are downloaded from https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/downloads.
Currently we don't update the toolchain to any versions newer than the one released here. We used the version 10.3-2021.07 with TF-A v2.6 release and will be updating to version 11.2-2022.02 with our upcoming v2.7 release which is planned for the end of May, 2022.

May 20 2022, 10:11 PM · Trusted Firmware A, TF-A Bug
soby-mathew added a comment to T989: Support SVE in non-secure world with CTX_INCLUDE_FPREGS=1.

When you have a S-EL2 based system with possibly multiple S-EL1 partitions, it would be complex to implement a scheme where in EL3 will restore the right S-EL1 context on taking a trap during lazy save mechanism. In such systems, it is easier for S-EL2 to implement such a scheme since it is the manager for S-EL1 contexts.

May 20 2022, 7:10 PM · Trusted Firmware A
okash added a comment to T989: Support SVE in non-secure world with CTX_INCLUDE_FPREGS=1.

Hey Olivier,

May 20 2022, 6:32 PM · Trusted Firmware A
madhukar-Arm added a comment to T991: Compiling atf for iMX8 using gcc-12..1 fails.

A similar issue was reported in the ticket https://developer.trustedfirmware.org/T984
Can you confirm if this issue is due to a bug in the toolchain itself?

May 20 2022, 4:33 PM · Trusted Firmware A, TF-A Bug

May 19 2022

LDong-Arm added a comment to T921: Supporting Non-Secure RTOS applications, integrated with Trusted Firmware-M, which want to use the FPU.

If you are still interested, we have an ongoing patch for adding an option to enable FPU coprocessors CP10/CP11: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/15243

May 19 2022, 10:38 AM · Trusted Firmware M

May 17 2022

Anton-TF edited the content of TF-M Security Patch Release Process.
May 17 2022, 11:02 AM

May 13 2022

sjl3110 added a comment to T990: Build TF-M 1.6 regression test failed with too long path on Windows.

Hi! Thanks for your draft! I created a patch: https://review.trustedfirmware.org/c/TF-M/tf-m-tests/+/15150. Does it meet your requirements?

May 13 2022, 5:56 AM · Trusted Firmware M

May 11 2022

heitbaum added a comment to T991: Compiling atf for iMX8 using gcc-12..1 fails.

Reported bug in gcc 12.1.0

May 11 2022, 11:54 AM · Trusted Firmware A, TF-A Bug
Yann-lms added a comment to T984: GCC12 build problem - PLAT=a80x0_mcbin.

The issue is related to this GCC ticket:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99578
Which is corrected in the official GCC 12.1 version.

May 11 2022, 8:52 AM · TF-A Bug, Trusted Firmware A

May 10 2022

ccli8 added a comment to T990: Build TF-M 1.6 regression test failed with too long path on Windows.

My modification is very draft, so I just list it here. Actually, the above has mentioned in total.

May 10 2022, 6:12 AM · Trusted Firmware M
KenLSoft added a comment to T990: Build TF-M 1.6 regression test failed with too long path on Windows.

Thanks for your feedback.

May 10 2022, 1:53 AM · Trusted Firmware M