Added support for target-specific config metadata #79
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
…ata.<target>.bootloader]
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.
Just a quick little change to allow bootimage to work with aarch64. I haven't been able to actually test it because I don't have a working aarch64-compatible bootloader (im using
bootloaderwhich is x86 only). Really I was just experimenting to see how much work it would be to add a raspi target to my toy OS, which I don't think I'm going to follow through with. I do know default x86_64 behavior still works as expected. Merge the changes if you like, reject them if you don't, I don't mind either way. Just figured I'd share it in case it's useful.