Repository navigation
Conversation
A bootloader config without WAKE_ON_GPIO uses 0, not 1. The default Raspberry Pi 4 bootloader images set WAKE_ON_GPIO=1 in their config, which is why most boards behave as if the default were 1. Fixes raspberrypi/rpi-eeprom#915
timg236
approved these changes
Nov 1, 2026
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.
Fixes raspberrypi/rpi-eeprom#915.
WAKE_ON_GPIOis documented asDefault: 1, but a bootloader config that does not set it halts withwake: 0and GPIO3 does not wake the board (see the logs in the issue). As @timg236 explained there, the code default is0; the default 2711 EEPROM images set it to1in their config:This changes the default to
0and says that the Pi 4 / Pi 400 / CM4 images set it to1, in the same way theNET_INSTALL_AT_POWER_ONentry describes its image default.