Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: Secure/Non-secure memory map #15

Open
dpretet opened this issue Oct 11, 2024 · 0 comments
Open

Feature: Secure/Non-secure memory map #15

dpretet opened this issue Oct 11, 2024 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@dpretet
Copy link
Owner

dpretet commented Oct 11, 2024

Today the core allows to define memory map to create zones only some master can access. However, a master could issues requests to a slave which would allowed in secure mode, but not in non-secure.

A secure attribute should be added to a memory map along it's allowed master to define the security level. APROT will be used to determine on the fly if the access is allowed or not.

@dpretet dpretet self-assigned this Oct 11, 2024
@dpretet dpretet added the enhancement New feature or request label Oct 11, 2024
@dpretet dpretet changed the title Feature: Secure/Non-secure Memory map Feature: Secure/Non-secure memory map Oct 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant