-
Notifications
You must be signed in to change notification settings - Fork 207
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
Handle case where mem_size_actual is 0 #363
Conversation
5da75c2
to
897ccc3
Compare
ec430cd
to
f123077
Compare
On newer machines, mem_size_actual is 0. This patch cooks up a value when that is the case, and shoves it in the right place. Without this MMU/etc hang on M3 due to not mapping the right region. Signed-off-by: Daniel Berlin <[email protected]>
f123077
to
1f75f4d
Compare
This should now be correct |
on j504 (M3 Macbook Pro 14-inch) I see |
4f95305
to
95d67cf
Compare
Looks like this is an issue with bootargs version/size then? |
Should be supeseded by #403. |
yes, it was. Complicated by the fact that early iboot versions on M3 devices did use revision 2 but used the longer command line length. Missing from #403 is updating |
also missing from #403 is replicating the correction of mem_size_actual (which I understand is for these old iBoot versions) in python side, since we're no longer patching the original bootargs and python sees 0 |
Handle case of no mem_size_actual
On newer machines, mem_size_actual is 0.
In this case, we need to use mem_size and mask to a page boundary.
This fixes MMU crash/hang on m3