clover: fix venus region location #49
Merged
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
…nd device DTS Signed-off-by: Nickolay Goppen <[email protected]>
minlexx
approved these changes
Jan 12, 2025
|
My TWRP of course does not load .mdt for venus, but reserved region is there - 8 MiB is 0x800000, so 0x9cc00000 + 0x800000 = 0x9d400000 which matches what I see here.. Thanks! |
|
The only question can be only if regular clover also has the same, but hopefully it is so.. |
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.
Current venus region location overlaps with ramoops region:
New location is taken from downstream kernel:
venus: loading from 0x000000009cc00000 to 0x000000009d100000