Skip to content

Collection of fixes for /memreserve/ handling #59

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

Merged
merged 6 commits into from
Feb 14, 2020

Conversation

kevans91
Copy link
Contributor

Testing and attempting to use dtc to parse out /memreserve/ nodes in the RPi DTB yielded a somewhat major issue in our dtc- there were no /memreserve/ in the output! This series fixes that and a couple of other issues with the handling; the commit messages describe the various issues I ran into.

Signed-off-by: Kyle Evans <kevans@FreeBSD.org>
This fixes writing out /memreserve/ when we're reading in from a DTB.

Signed-off-by: Kyle Evans <kevans@FreeBSD.org>
If we failed and hit the parse_error, then we'd still push back whatever
ended up in the start/length variables.

Signed-off-by: Kyle Evans <kevans@FreeBSD.org>
Signed-off-by: Kyle Evans <kevans@FreeBSD.org>
Previously, we'd end up writing the start twice rather than the start
followed by the length.

Signed-off-by: Kyle Evans <kevans@FreeBSD.org>
Otherwise these can and should be interpreted by any dts reader as decimal
constants and misinterpreted, rather than as hex constants (as implied by
PRIx64).

Signed-off-by: Kyle Evans <kevans@FreeBSD.org>
@davidchisnall davidchisnall merged commit 0060471 into davidchisnall:master Feb 14, 2020
@kevans91 kevans91 deleted the memreserv branch February 18, 2020 19:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants