Page MenuHomePhabricator

Trusted Firmware-m Isolation Level 2
Updated 143 Days AgoPublic

This document has been moved to /w/tf_m/recyclebin/trusted_firmware-m_isolation_level_2/. You can edit it to put new content here, or use history to revert to an earlier version.

Last Author
KenLSoft
Last Edited
Jun 4 2021, 12:35 AM

Event Timeline

KenLSoft changed the edit policy from "All Users" to "Custom Policy".Feb 19 2019, 10:20 AM
KenLSoft added a project: Restricted Project.
KenLSoft added subscribers: ashutoshksingh, KenLSoft, wmnt.
KenLSoft edited the content of this document. (Show Details)Feb 19 2019, 10:40 AM
KenLSoft edited the content of this document. (Show Details)Mar 14 2019, 7:59 AM
KenLSoft edited the content of this document. (Show Details)
KenLSoft edited the content of this document. (Show Details)Mar 21 2019, 7:08 AM
KenLSoft edited the content of this document. (Show Details)Mar 21 2019, 7:23 AM
KenLSoft edited the content of this document. (Show Details)Mar 25 2019, 8:44 AM
KenLSoft edited the content of this document. (Show Details)Mar 26 2019, 6:06 AM
KenLSoft edited the content of this document. (Show Details)Mar 27 2019, 1:33 PM
KenLSoft changed the edit policy from "Custom Policy" to "Custom Policy".Mar 28 2019, 7:22 AM
Summer-ARM edited the content of this document. (Show Details)Mar 28 2019, 7:26 AM
sbulgin-tfm added a subscriber: sbulgin-tfm.EditedJun 8 2020, 4:47 PM

Curious, noted is printf to be redesigned. What about malloc, calloc, and other libc functions that currently rely on a common RW section. That is the App RoT won't have access (and shouldn't have access) to say a common heap through libc. Has this been considered?