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 <[email protected]>
Kind regards,
Petr
[1]
https://lore.kernel.org/all/[email protected]/
> Reviewed-by: Simon Glass <[email protected]>
> Signed-off-by: David Heidelberg <[email protected]>
> ---
> 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
