HI Richard, A Pull request for marking region0 as secure in OP-TEE is raised here: https://github.com/OP-TEE/optee_os/pull/7838
Regards, Sahil Malhotra > -----Original Message----- > From: Richard Weinberger <[email protected]> > Sent: 09 June 2026 15:46 > To: Sahil Malhotra <[email protected]>; Ye Li (OSS) > <[email protected]> > Cc: U-Boot Mailing List <[email protected]>; Alice Guo > <[email protected]>; Peng Fan <[email protected]>; > [email protected]; Ye Li <[email protected]> > Subject: [EXT] Re: TZASC misconfiguration on i.mx8m > > Caution: This is an external email. Please take care when clicking links or > opening attachments. When in doubt, report the message using the 'Report > this email' button > > > On Dienstag, 9. Juni 2026 12:12 Ye Li wrote: > > >> Why can't this optee patch apply to optee upstream? It is optee > > >> using secure memory, then it should be optee's responsibility to > > >> configure trustzone correctly. Optee can't depends on default value > > >> of trustzone, since trustzone is not enabled by optee. > > > > > > Sorry for the harsh words, but that's *your* job at NXP to sort out. > > > You seem to ignore upstream. > > > > > I'm not working in optee. As I mentioned early, NXP has decided to fix > > it in optee. That's what you find the patch in NXP downstream tree. I > > think Sahil will try to upstream it later. > > Ok! :) > Maybe Sahil can shed light on the issue. > I find it kinda odd that NXP is only focusing on their tree despite the > upstream > solution. > > Thanks, > //richard > > -- > sigma star gmbh | Eduard-Bodem-Gasse 6, 6020 Innsbruck, AUT UID/VAT Nr: > ATU 66964118 | FN: 374287y >
smime.p7s
Description: S/MIME cryptographic signature
