u-boot: Remove bbappend after RPi 5 was re-enabled upstream #414
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
|
Hi @eigendude, |
TheYoctoJester
approved these changes
Nov 4, 2024
RPi 5 was re-enabled in the following commit: * agherzan/meta-raspberrypi@6d59364
TheYoctoJester
force-pushed
the
fix-rpi5
branch
from
8db8520
to
c6d3dc4
Compare
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.
Description
RPi 5 was re-enabled upstream in the following commit:
So we don't need the bbappend to disable it anymore.
How has this been tested?
Tested with U-boot v2024.04 from the meta-lts-mixins layer.
Before, when building my OS for the RPi 5, I get the error:
After:
Bitbake recipes parse correctly.
Runtime tested the resulting image on the RPi 5 (at least I got as far as getting stuck in the bootloader).