Introduce Pixel config fragment for chainloading u-boot
v4 cover Introduce Pixel config fragment for chainloading u-boot
Snapdragon Google Pixel bootloaders require the TEXT_OFFSET to be exactly 0x80000. Without this, U-Boot or kernels will fail to load.
This patchset documents Pixel 3 and Pixel 3 XL and adds the necessary config fragment along with usage instructions.
It has been tested on Pixel 3, 3 XL (by me), and Pixel 5 (by Petr Vorel).
The corresponding DTS files (sdm845-google-blueline and crosshatch) have already been merged into the Linux -next, so mainline U-Boot will receive these devices support soon.
---
Changes in v4:
- s/CONFIG_TEXT_OFFSET/CONFIG_TEXT_BASE/ in commit message (Casey)
- Link to v3: https://lore.kernel.org/r/[email protected]
Changes in v3:
- Renamed google-pixel3.config to google-pixel.config as it's not limited to Pixel 3 / 3 XL, but also 5 and possibly others.
- Reworked the documentation. (Casey)
- Reworded commit message. (Casey)
- Link to v2: https://lore.kernel.org/u-boot/[email protected]/
Changes in v2:
- Added documentation of Pixel 3 / 3 XL into doc/board/qualcomm. (Casey)
- Link to v1: https://lore.kernel.org/u-boot/[email protected]/
---
David Heidelberg (2):
doc: board: qualcomm: document Pixel 3 / 3 XL support
configs: Add google-pixel fragment config for Pixel 3, 3 XL, 5
board/qualcomm/google-pixel.config | 5 +++++ doc/board/qualcomm/board.rst | 20 ++++++++++++++++++++ 2 files changed, 25 insertions(+)
---
base-commit: 53c0d5b387956bb4070a943b61991898373a20e2
change-id: 20260107-pixel-config-4b058ecc4e1b
Best regards,
Signature · 1 line
David Heidelberg <[email protected]>
PATCH v4 1/2 doc: board: qualcomm: document Pixel 3 / 3 XL support
U-Boot does work on Qualcomm 845-based Pixel 3 and 3 XL.
--- doc/board/qualcomm/board.rst | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+)
doc/board/qualcomm/board.rst +20 -0
@@ -38,6 +38,25 @@ with appended dtb, so let's mimic linux to satisfy stock bootloader. Boards ------ +Pixel 3 (blueline) and Pixel 3 XL (crosshatch) +^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ +blueline refers to the Google Pixel 3, and crosshatch to the Pixel 3 XL, both +powered by the Qualcomm SDM845 SoC. + +These devices use the common qcom_defconfig with the google-pixel.config +fragment for configuration. + +Use the following commands:: + + make CROSS_COMPILE=aarch64-linux-gnu- O=.output qcom_defconfig google-pixel.config qcom-phone.config + +The DTB is called: + + - "sdm845-google-blueline.dtb" (Pixel 3) + - "sdm845-google-crosshatch.dtb" (Pixel 3 XL) + +More information can be found on the `Google Pixel 3 page`_. + starqlte ^^^^^^^^
@@ -131,5 +150,6 @@ Other devices with boot image version 2 can be built like this example:: fastboot flash boot boot.img fastboot erase dtbo +.. _Google Pixel 3 page: https://en.wikipedia.org/wiki/Pixel_3 .. _Samsung S9 page: https://en.wikipedia.org/wiki/Samsung_Galaxy_S9 .. _DragonBoard 845c page: https://www.96boards.org/product/rb3-platform/
Signature · 1 line
2.51.0
Re: [PATCH v4 1/2] doc: board: qualcomm: document Pixel 3 / 3 XL support
Hi all,
Hopefully we add other Pixels in the future.
Kind regards,
Petr
PATCH v4 2/2 configs: Add google-pixel fragment config for Pixel 3, 3 XL, 5
In reply to David HeidelbergIntroduce a fragment config for the Pixel 3, Pixel 3 XL, Pixel 5.
On these devices, U-Boot is chainloaded via fastboot. However, due to additional requirements added by Google, the image header must have a specific value for the text offset.
This is solved by setting CONFIG_TEXT_BASE to 0x80080000 in U-Boot.
--- board/qualcomm/google-pixel.config | 5 +++++ 1 file changed, 5 insertions(+)
board/qualcomm/google-pixel.config new file +5 -0
@@ -0,0 +1,5 @@ +# Enables chainloading of U-Boot on Google Pixel phones using +# newer bootloaders (Android Q/R) +# Use for following devices: Pixel 3 (blueline), Pixel 3 XL (crosshatch), +# Pixel 5 (redfin)... +CONFIG_TEXT_BASE=0x80080000
Signature · 1 line
2.51.0
Re: [PATCH v4 2/2] configs: Add google-pixel fragment config for Pixel 3, 3 XL, 5
Hi all,
Quoted 6 lines
Introduce a fragment config for the Pixel 3, Pixel 3 XL, Pixel 5.
On these devices, U-Boot is chainloaded via fastboot. However, due to additional requirements added by Google, the image header must have a specific value for the text offset.
This is solved by settingCONFIG_TEXT_BASEto0x80080000in U-Boot.
Yeah, to workaround for kernel change 120dc60d0bdb ("arm64: get rid of TEXT_OFFSET") because trying to put it back [1] was rejected.
Thanks!
Kind regards,
Petr
[1] https://lore.kernel.org/all/[email protected]/
Quoted 17 lines
Reviewed-by Simon Glass <[email protected]>Signed-off-by David Heidelberg <[email protected]>--- board/qualcomm/google-pixel.config | 5 +++++ 1 file changed, 5 insertions(+)board/qualcomm/google-pixel.config new file +5
-0@@ -0,0 +1,5 @@ +# Enables chainloading of U-Boot on Google Pixel phones using +# newer bootloaders (Android Q/R) +# Use for following devices: Pixel 3 (blueline), Pixel 3 XL (crosshatch), +# Pixel 5 (redfin)... +CONFIG_TEXT_BASE=0x80080000
Casey Connolly
AppliedQuoted 9 lines · David Heidelberg
Snapdragon Google Pixel bootloaders require the
TEXT_OFFSETto be exactly0x80000. Without this, U-Boot or kernels will fail to load.This patchset documents Pixel 3 and Pixel 3 XL and adds the necessary config fragment along with usage instructions.
It has been tested on Pixel 3, 3 XL (by me), and Pixel 5 (by Petr Vorel).
[...]
Applied, thanks!
[1/2] doc: board: qualcomm: document Pixel 3 / 3 XL support
https://source.denx.de/u-boot/custodians/u-boot-snapdragon/-/commit/500d2e5e5546 [2/2] configs: Add google-pixel fragment config for Pixel 3, 3 XL, 5 https://source.denx.de/u-boot/custodians/u-boot-snapdragon/-/commit/338dbbba8787
Best regards,
Signature · 1 line
// Casey (she/they)