Skip to contentSkip to conversation

doc: board: qualcomm: document Pixel 3 / 3 XL support

RFC PATCH Superseded David Heidelberg 2 participants 4 messages Aug 2, 2025 – Aug 4, 2025

v2 of 4 Superseded Latest is v4 →

lore
Share & tools
lore
#0 lore raw

RFC PATCH v2 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 | 26 ++++++++++++++++++++++++++
 1 file changed, 26 insertions(+)
doc/board/qualcomm/board.rst +26 -0
index 642c5095261..12ff15f49fc 100644
@@ -38,6 +38,31 @@ with appended dtb, so let's mimic linux to satisfy stock bootloader.
 Boards
 ------
 
+blueline
+^^^^^^^^
+The blueline is a Google Pixel 3 phone,
+based on the Qualcomm SDM845 SoC.
+
+This device is supported by the common qcom_defconfig in combination
+with google-pixel3.config config fragment.
+
+The DTB is called "sdm845-google-blueline.dtb"
+
+More information can be found on the `Google Pixel 3 page`_.
+
+crosshatch
+^^^^^^^^^^
+The crosshatch is a Google Pixel 3 XL phone,
+based on the Qualcomm SDM845 SoC.
+
+This device is supported by the common qcom_defconfig in combination
+with google-pixel3.config config fragment.
+
+The DTB is called "sdm845-google-crosshatch.dtb"
+
+More information can be found on the `Google Pixel 3 page`_.
+
+
 starqlte
 ^^^^^^^^
 
@@ -131,5 +156,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.50.1
#1 lore raw

RFC PATCH v2 2/2 configs: Add google-pixel3 fragment config for Pixel 3 / 3 XL

Introduce a fragment config for the Pixel 3 and Pixel 3 XL.

On these devices, U-Boot must be chainloaded via Fastboot. However, due to a Fastboot bug, U-Boot won’t start unless a specific condition is met.

To work around this, U-Boot must provide a TEXT_OFFSET of 0x00080000, which allows Fastboot to successfully launch U-Boot.

Instead of:

$ make CROSS_COMPILE=aarch64-linux-gnu- O=.output qcom_defconfig qcom-phone.config
do
$ make CROSS_COMPILE=aarch64-linux-gnu- O=.output qcom_defconfig google-pixel3.config qcom-phone.config
---
 board/qualcomm/google-pixel3.config | 3 +++
 1 file changed, 3 insertions(+)
 create mode 100644 board/qualcomm/google-pixel3.config
board/qualcomm/google-pixel3.config new file +3 -0
new file mode 100644
index 00000000000..2dc71c65d23
@@ -0,0 +1,3 @@
+# Pixel 3 (blueline) and Pixel 3 XL (crosshatch) will fail to
+# chainload u-boot on the Q or R bootloader if TEXT_BASE offset is missing.
+CONFIG_TEXT_BASE=0x80080000
Signature · 1 line
2.50.1
#2 lore raw

Re: [RFC PATCH v2 2/2] configs: Add google-pixel3 fragment config for Pixel 3 / 3 XL

Quoted 3 lines · David Heidelberg

Introduce a fragment config for the Pixel 3 and Pixel 3 XL.

On these devices, U-Boot must be chainloaded via Fastboot. However, due to

s/must be/is/g (be descriptive rather than prescriptive).

Quoted 1 line

a Fastboot bug, U-Boot won’t start unless a specific condition is met.

additional requirements added by google, the image header must have a specific value for the text offset.>

Quoted 1 line

To work around this, U-Boot must provide a TEXT_OFFSET of 0x00080000,

this is solved by setting CONFIG_TEXT_OFFSET in U-Boot.

Kind regards,
// Casey (she/they)

Quoted 22 lines

which allows Fastboot to successfully launch U-Boot.

Instead of:

$ make CROSS_COMPILE=aarch64-linux-gnu- O=.output qcom_defconfig qcom-phone.config
do
$ make CROSS_COMPILE=aarch64-linux-gnu- O=.output qcom_defconfig google-pixel3.config qcom-phone.config
---
  board/qualcomm/google-pixel3.config | 3 +++
  1 file changed, 3 insertions(+)

create mode 100644 board/qualcomm/google-pixel3.config

board/qualcomm/google-pixel3.config new file +3 -0
new file mode 100644
index 00000000000..2dc71c65d23
@@ -0,0 +1,3 @@
+# Pixel 3 (blueline) and Pixel 3 XL (crosshatch) will fail to
+# chainload u-boot on the Q or R bootloader if TEXT_BASE offset is missing.
+CONFIG_TEXT_BASE=0x80080000
#3 lore raw
In reply to David Heidelberg

Hi David,

Thanks for respinning these and adding the docs, some suggestions inline (sorry for the nitpicks).

Quoted 12 lines · David Heidelberg

U-Boot does work on Qualcomm 845-based Pixel 3 and 3 XL.

---
  doc/board/qualcomm/board.rst | 26 ++++++++++++++++++++++++++
  1 file changed, 26 insertions(+)
doc/board/qualcomm/board.rst +0 -0
index 642c5095261..12ff15f49fc 100644

doc/board/qualcomm/board.rst with appended dtb, so let's mimic linux to satisfy stock bootloader. · line 41

Quoted 4 lines
doc/board/qualcomm/board.rst +1 -0
@@ -38,6 +38,31 @@ with appended dtb, so let's mimic linux to satisfy stock bootloader.
  Boards
  ------
 
+blueline

Pixel 3 (blueline) and Pixel 3XL (crosshatch) would be a better title I think (starqlte is not the best example imo). These two can be combined into one section.

doc/board/qualcomm/board.rst with appended dtb, so let's mimic linux to satisfy stock bootloader. · line 44

Quoted 3 lines
doc/board/qualcomm/board.rst +3 -0
+^^^^^^^^
+The blueline is a Google Pixel 3 phone,
+based on the Qualcomm SDM845 SoC.

The Pixel 3/3XL are based on the Snapdragon 845 SoC. They are supported by the generic qcom_defconfig with the google-pixel3.config config fragment::

make CROSS_COMPILE=aarch64-linux-gnu- O=.output qcom_defconfig
google-pixel3.config qcom-phone.config

	make CROSS_COMPILE=aarch64-linux-gnu- O=.output -j$(nproc) 

DEVICE_TREE=qcom/sdm845-google-blueline

If building for crosshatch use ``DEVICE_TREE=qcom/sdm845-google-crosshatch`` instead.

Kind regards,
// Casey (she/they)

Quoted 31 lines
doc/board/qualcomm/board.rst +22 -0
+
+This device is supported by the common qcom_defconfig in combination
+with google-pixel3.config config fragment.
+
+The DTB is called "sdm845-google-blueline.dtb"
+
+More information can be found on the `Google Pixel 3 page`_.
+
+crosshatch
+^^^^^^^^^^
+The crosshatch is a Google Pixel 3 XL phone,
+based on the Qualcomm SDM845 SoC.
+
+This device is supported by the common qcom_defconfig in combination
+with google-pixel3.config config fragment.
+
+The DTB is called "sdm845-google-crosshatch.dtb"
+
+More information can be found on the `Google Pixel 3 page`_.
+
+
  starqlte
  ^^^^^^^^
 
@@ -131,5 +156,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/