firehose: Handle multiple primary bootloaders #87
Conversation
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
andersson
force-pushed
the
for-linux-msm/multiple-primary-bootloaders
branch
from
f76d176 to
d1b4bb2
Compare
Builds with multiple copies of the primary bootloader does not make sense, but after successfully flashing all the partitions of such build it makes more sense to make one of them bootable, at least more than skipping the step and saying that none was found. Pick the first found primary bootloader and warn the user about the situation. Signed-off-by: Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>
andersson
force-pushed
the
for-linux-msm/multiple-primary-bootloaders
branch
from
d1b4bb2 to
969fcb5
Compare
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.
Builds with multiple copies of the primary bootloader does not make sense, but after successfully flashing all the partitions of such build it makes more sense to make one of them bootable, at least more than skipping the step and saying that none was found.
Pick the first found primary bootloader and warn the user about the situation.