Retain vendor notices in Raspberry Pi firmware build outputs #103
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
kaiba/kaiba-provisioning!103
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "codex/retain-firmware-build-notices"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The EEPROM release and probe-bundle recipes copy Raspberry Pi firmware into new outputs without retaining its vendor licensing materials. Add adjacent notices directories containing the complete upstream texts and a component-to-file map, and expose the probe notices in the provisioning package.
Verify that the frozen probe bootcode is byte-identical to the EEPROM submodule's recovery firmware before assigning its custom firmware terms. Keep Apache-2.0 material separate for usbboot, including a hash-pinned license from the exact revision supplying update-pieeprom.sh. Preserve the original firmware bytes, EEPROM release manifests, and the probe bundle's two-file layout and digest format.
Validation:
The vendor's "without modification" grant still needs clarification before redistributing configured/signed variants. This change retains notices; it does not resolve that permission question. Public v0.1.6 release notices and operational payload retention are handled independently in #102.