Add i.MX93 support + bugfixes #50
Open
Conversation
This file contains 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
Signed-off-by: Indan Zupancic <[email protected]>
Depending on the generated code of seL4_MessageInfo_new(), it may or may not clobber r0/x0. Perhaps only a problem for RELEASE=OFF builds, but it makes debugging other problems harder by adding myserious crashes. Signed-off-by: Indan Zupancic <[email protected]>
The function will return and crash because there is nothing to return to and apparantly the sel4runtime doesn't implement a soft landing. Test still works with crashing processes and with debugging disabled it's invisible. But very confusing when trying to debug any kind of other problems and enabling debugging. Signed-off-by: Indan Zupancic <[email protected]>
This was referenced Dec 2, 2024
lsf37
approved these changes
Dec 2, 2024
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.
The i.MX93 only has up to 2 cores.
I can split the bugfixes into a separate PR if required, that would make more sense I suppose. The page mapping test is the last one crashing when RELEASE=OFF, so I could also just wait with the bugfixes till I fixed that one too.