From: Petr Vorel <petr.vorel@gmail.com>
To: david@ixit.cz
Cc: Sumit Garg <sumit.garg@kernel.org>,
u-boot-qcom@groups.io, u-boot@lists.denx.de,
Casey Connolly <casey.connolly@linaro.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Tom Rini <trini@konsulko.com>,
Luca Weiss <luca.weiss@fairphone.com>,
Simon Glass <sjg@chromium.org>,
Petr Hodina <petr.hodina@protonmail.com>,
Matthew Croughan <matt@croughan.sh>,
phone-devel@vger.kernel.org,
Simon Glass <simon.glass@canonical.com>
Subject: Re: [PATCH v4 2/2] configs: Add google-pixel fragment config for Pixel 3, 3 XL, 5
Date: Fri, 9 Jan 2026 22:05:01 +0100 [thread overview]
Message-ID: <20260109210501.GB140231@pevik> (raw)
In-Reply-To: <20260108-pixel-config-v4-2-76a2212b69a5@ixit.cz>
Hi all,
> 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 setting CONFIG_TEXT_BASE to 0x80080000 in 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!
Reviewed-by: Petr Vorel <petr.vorel@gmail.com>
Kind regards,
Petr
[1] https://lore.kernel.org/all/20251006-arm64-text-offset-v1-1-bf0e8a27383b@oss.qualcomm.com/
> Reviewed-by: Simon Glass <simon.glass@canonical.com>
> Signed-off-by: David Heidelberg <david@ixit.cz>
> ---
> board/qualcomm/google-pixel.config | 5 +++++
> 1 file changed, 5 insertions(+)
> diff --git a/board/qualcomm/google-pixel.config b/board/qualcomm/google-pixel.config
> new file mode 100644
> index 00000000000..999d4e45268
> --- /dev/null
> +++ b/board/qualcomm/google-pixel.config
> @@ -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
next prev parent reply other threads:[~2026-01-09 21:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 22:13 [PATCH v4 0/2] Introduce Pixel config fragment for chainloading u-boot David Heidelberg via B4 Relay
2026-01-08 22:13 ` [PATCH v4 1/2] doc: board: qualcomm: document Pixel 3 / 3 XL support David Heidelberg via B4 Relay
2026-01-09 21:00 ` Petr Vorel
2026-01-08 22:13 ` [PATCH v4 2/2] configs: Add google-pixel fragment config for Pixel 3, 3 XL, 5 David Heidelberg via B4 Relay
2026-01-09 21:05 ` Petr Vorel [this message]
2026-01-16 18:03 ` [PATCH v4 0/2] Introduce Pixel config fragment for chainloading u-boot Casey Connolly
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260109210501.GB140231@pevik \
--to=petr.vorel@gmail.com \
--cc=casey.connolly@linaro.org \
--cc=david@ixit.cz \
--cc=luca.weiss@fairphone.com \
--cc=matt@croughan.sh \
--cc=neil.armstrong@linaro.org \
--cc=petr.hodina@protonmail.com \
--cc=phone-devel@vger.kernel.org \
--cc=simon.glass@canonical.com \
--cc=sjg@chromium.org \
--cc=sumit.garg@kernel.org \
--cc=trini@konsulko.com \
--cc=u-boot-qcom@groups.io \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox