use Flattened DeviceTrees to determine the hardware specification #201
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
Qemu stores the device tree at the beginning of the RAM. Consequently, we have to move the loader to create space for the device tree. Afterwards, the device tree can be used to determine the UART address and the memory regions.
The guest loader is able to load the an initial ramdisk and announce the location by the device tree. The loader checks if the initrd contains a valid elf file and boot it. see https://qemu.readthedocs.io/en/latest/system/guest-loader.html
|
bors r+ |
|
Build succeeded: |
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.
Qemu stores the device tree at the beginning of the RAM. Consequently, we have to move the loader to create space for the device tree. Afterwards, the device tree can be used to determine the UART address and the memory regions.