Repository navigation
Prefer U-Boot machine type for CC2 hardware detection - #453
Merged
suchmememanyskill merged 1 commit intoOct 30, 2026
Merged
Conversation
✅ Build ArtifactsBranch:
|
suchmememanyskill
marked this pull request as ready for review
October 30, 2026 22:07
jamesturton
approved these changes
Oct 30, 2026
This branch was successfully deployed
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
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.
Prefer the U-Boot
machine_typesaved by the installer when configuring enclosure hardware:centauri-carbon-2enables it andcentauri-2disables it. Fall back to the existing active-low GPIO check if the setting is missing, unreadable, or unrecognized.Add the
u-boot-fw-utilsruntime dependency. CANVAS probing and the first-boot marker behavior are unchanged.Stacked on #450 (Backup ELEGOO.txt in .swu.sig).
Validation: shell syntax and diff checks passed, plus 14 mocked behavior checks covering both known models, fallback paths, GPIO failures, CANVAS configuration, and init actions. No firmware build or hardware test performed.