Boot order preference via sd:/boot_order.txt #39
Closed
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
|
I don't think I'm inclined to merge this -- definitely feel free to use this for your personal use, I mean, that's the point of open-source projects. From my point-of-view:
|
|
Sanity check, though, @TuxSH ^ |
|
Understood. Just to make it clear: the goal of this is specifically to not move the regular boot.firm (Luma) so that it can safely be updated by the Universal Updater. Your second point would break this, that’s why I made the fork in the first place :) |
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.
Directly addresses / resolves #38
With this PR proposal, anyone can override the firmware to be booted by B9S.
By default, it will always boot sd:/boot.firm.
But by creating a sd:/boot_order.txt file, you can specify a list of firmwares to be loaded and the first one that is available is going to be selected for loading.
For example, your sd:/boot_order.txt file could look like:
This list acts just like your PCs BIOS: first one in order available gets booted, all the others are skipped.
And of course, if none are available, B9S will always boot the boot.firm firmware so it does not affect its standard behavior.
Note: currently there is no integrity check being made in the process, which means that if the file you are pointing exists on the SD card and is not a valid firmware, the console will NOT boot to boot.firm file in fallback (you will encounter the notification LED status informing that the boot has failed, and B9S will try to boot from CTRNAND as usual for a corrupted firmware).