Materialize explicit runtime DeviceTree values before committing RAM - #3
Merged
Merged
Conversation
NiSeullent
added a commit
that referenced
this pull request
Sep 14, 2026
Materialize explicit runtime DeviceTree values before committing RAM
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
2 participants
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.
Add a Core-owned runtime DeviceTree materializer. Each template replacement must identify the exact source hash and original property offset and supply explicit value bytes. The implementation preserves literals, rejects unknown/duplicate/missing bindings, prepares a separate bounded tree, and validates it before copying into a declared destination reservation. Returned errors preserve the entire destination.
The caller's guest mapping and declared reservation are kept distinct from actual slice size and allocator ownership. No expression evaluator, zero fallback, ISE dependency or boot-readiness API is introduced. Existing strict runtime dimensions are preserved; the original macOS 27 tree and live allocation/provider state are not yet accepted by this change.
Nine authored tests, all existing Core targets, host no_std and x86 UEFI no_std checks pass in a fresh standalone clone. File inventory hashes and clean checkout are verified. Guest execution of the produced tree and complete normal startup remain subsequent integration work.