The patch stack is still a work in progress so BL1 is the only fixed image so far, but BL2 and BL31 need the same treatment. Your best bet until I get around to applying these fixes to the remaining images is the current workaround (TF_LDFLAGS="--no-warn-rwx-segment").
Open Tasks
Unbreak Now! (1)
Needs Triage (14)
- No Projects
- Fri, Jan 13, 12:01 AM
- Nov 25 2022, 8:15 AM
- Sep 22 2022, 1:05 PM
Recent Activity
Wed, Jan 25
Tue, Jan 24
Fri, Jan 20
Thu, Jan 19
Wed, Jan 18
Fri, Jan 13
Thu, Jan 12
Mon, Jan 9
Sun, Jan 8
Thanks, good to know. So, 2.9 will likely carry a fix? Is there a better patch I can use already (the one referenced does not directly appear to solve the issue)?
Hi Jan, sorry for the delay. This is currently in progress under the mixed-rwx topic: https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/18661/5
What's the status of this? Currently trying to build TF-A against the bookworm toolchain, and there the warning is even fatal. For now I'm working around it with this patch:
Fri, Jan 6
Wed, Jan 4
Tue, Jan 3
I want to find a way to clean a memory region in TF-A firmware.
Fri, Dec 30
Dec 19 2022
I want to find a way to clean a memory region in TF-A firmware.
Can you elaborate what you mean by "clean" ?
From the description it seems to be a simple memset, in which case data may remain in caches.
Does the requested operation need to complete to memory e.g. involving cache clean?