pieeprom-2026-09-10: 2712: Move rpi-fw-crypto functions to secure RAM (latest) - #878
Merged
Merged
Conversation
… (latest) * arm_loader: Reapply call to get_turbo_clocks when querying min clock This is needed for pixel clock when running with force_turbo=1 When we report min=max to kernel, it will never set them, so we don't know about its clock requirements See: raspberrypi/linux#7564 * Move crypto functions to secure RAM All the crypto functions on 2712 now reside in the protected RAM region. There is no change to how they are used with rpi-fw-crypto. * Fix TFTP signed booting When TFTP booting with signed boot, resolving the prefix should be done using the existance of boot.img rather than config.txt. See: #857 * 2712: Add RP1 fw init fatal error handler If the RP1 CHIP_ID is not recogized during the I2C init phase then stop with fatal error code. Previously, the bootloader would continue and fail with an assert intead. * Print SFDP EEPROM capacity Print the capacity of the SPI flash chip from the SFDP table when available. The firmware does not rely on any SFDP data, but it can be helpful to see it when attempting to identify the SPI flash chip.
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
1 participant
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.
This is needed for pixel clock when running with force_turbo=1 When we report min=max to kernel, it will never set them, so we don't know about its clock requirements
See: Pi 3: HDMI pixel clock stuck at firmware minimum after modeset on 6.18 — monitor reports "Mode Not Supported" linux#7564
All the crypto functions on 2712 now reside in the protected RAM region. There is no change to how they are used with rpi-fw-crypto.
When TFTP booting with signed boot, resolving the prefix should be done using the existance of boot.img rather than config.txt.
See: CM5 Signed-boot network boot over TFTP aborts unconditionally ("Read boot.img failed", Error 12) #857
If the RP1 CHIP_ID is not recogized during the I2C init phase then stop with fatal error code. Previously, the bootloader would continue and fail with an assert intead.
Print the capacity of the SPI flash chip from the SFDP table when available. The firmware does not rely on any SFDP data, but it can be helpful to see it when attempting to identify the SPI flash chip.