Introduce a defconfig 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. Clearing the framebuffer improves the Pixel 3 experience, as it prevents collisions with the Fastboot logo left on the display. Instead of: $ make CROSS_COMPILE=aarch64-linux-gnu- O=.output qcom_defconfig qcom-phone.config do $ make CROSS_COMPILE=aarch64-linux-gnu- O=.output pixel3_defconfig qcom-phone.config Cc: Neil Armstrong <neil.armstr...@linaro.org> Cc: Casey Connolly <casey.conno...@linaro.org> Signed-off-by: David Heidelberg <da...@ixit.cz> --- configs/pixel3_defconfig | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 configs/pixel3_defconfig diff --git a/configs/pixel3_defconfig b/configs/pixel3_defconfig new file mode 100644 index 00000000000..9c0c8ca63c4 --- /dev/null +++ b/configs/pixel3_defconfig @@ -0,0 +1,13 @@ +# Pixel 3 has special requirement to have TEXT_BASE set for the fastboot. + +#include "qcom_defconfig" + +# Otherwise buildman thinks this isn't an ARM platform +CONFIG_ARM=y + +# some Pixel 3 bootloaders aren't able to start without TEXT_BASE +CONFIG_TEXT_BASE=0x80080000 +CONFIG_HAVE_SYS_UBOOT_START=y + +# fastboot logo distorts u-boot output +# CONFIG_NO_FB_CLEAR is not set -- 2.50.0
