Repository navigation
Documented that the Cortex-A35 module ports provide no module isolation - #111
Merged
fdesbiens merged 1 commit intoOct 24, 2026
Merged
Conversation
Chapter 1 of the Modules guide said that memory protection confines a module whenever it is specified, with no port caveat. The Cortex-A35 and Cortex-A35 SMP module ports have never implemented it: modules run at the Module Manager's exception level, call it directly, and get no memory management configuration. Chapter 1 now says so, gives the behaviour up to 6.5.2.202603, where both properties are accepted without effect, and after eclipse-threadx/threadx#816, where they are refused, and states that modules on these ports must be trusted. The Antora site build reports no errors or warnings, and the paragraph renders in chapter 1. Assisted-by: Claude Code (Opus 5.5) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Chapter 1 of the Modules guide said that memory protection confines a module whenever it is specified, with no port caveat. The Cortex-A35 and Cortex-A35 SMP module ports have never implemented it: modules run at the Module Manager's exception level, call it directly, and get no memory management configuration.
Chapter 1 now says so, gives the behaviour up to 6.5.2.202603, where both properties are accepted without effect, and after eclipse-threadx/threadx#816, where they are refused, and states that modules on these ports must be trusted. It should merge after eclipse-threadx/threadx#817.
The Antora site build reports no errors or warnings, and the paragraph renders in chapter 1.