pieeprom-2026-01-16: 2712: Assume eMMC for CM4/CM5 (latest)#795
Merged
timg236 merged 1 commit intoraspberrypi:masterfrom Jan 16, 2026
Merged
pieeprom-2026-01-16: 2712: Assume eMMC for CM4/CM5 (latest)#795timg236 merged 1 commit intoraspberrypi:masterfrom
timg236 merged 1 commit intoraspberrypi:masterfrom
Conversation
* Assume eMMC for CM4/CM5 non-lite Attempt the fast path by skipping the SD interface condition command timeout on CM4/CM5 (non-lite) modules and enable eMMC mode directly. This saves ~250ms of the boot time. * Don't stomp on RTC alarm state Preserve the RTC's alarm state so that it can be queried by the rpi-rtc driver. See: raspberrypi/firmware#2011 * arm_loader: Apply rpifwcrypto lock permissions GET/SET USER OTP Previously, the GET/SET user OTP mailboxes would provide access to the device unique private key. Update the mailbox API to fail if the key has been locked via lock_device_private_key=1 in config.txt or the associated mailbox call. GET/SET user OTP fails by setting the result tag to the standard error code (0x80000000). The dedicate GET/SET private key continue to fail the entire mailbox operation to force vcmailbox to exit with a non-zero error code. * cm5: Add support for 8-bit bus width eMMC
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.
Attempt the fast path by skipping the SD interface condition command timeout on CM4/CM5 (non-lite) modules and enable eMMC mode directly. This saves ~250ms of the boot time.
Preserve the RTC's alarm state so that it can be queried by the rpi-rtc driver. See: Raspberry Pi 5: RTC wakealarm works fine but /proc/driver/rtc shows alrm_pending: no firmware#2011
Previously, the GET/SET user OTP mailboxes would provide access to the device unique private key. Update the mailbox API to fail if the key has been locked via lock_device_private_key=1 in config.txt or the associated mailbox call. GET/SET user OTP fails by setting the result tag to the standard error code (0x80000000). The dedicate GET/SET private key continue to fail the entire mailbox operation to force vcmailbox to exit with a non-zero error code.