On Thu, Oct 22, 2020 at 11:03 AM Simon Glass sjg@chromium.org wrote:
At present CONFIG_CHROMEOS is used to determine whether verified boot is in use. The code to implement that is not in U-Boot mainline.
However, it is useful to be able to boot a Chromebook in developer mode in U-Boot mainline without needing the verified boot code.
To allow this, use CONFIG_CHROMEOS_VBOOT to indicate that verified boot should be used, and CONFIG_CHROMEOS to indicate that the board supports Chrome OS. That allows us to define CONFIG_CHROMEOS on coral.
Signed-off-by: Simon Glass sjg@chromium.org
Changes in v2:
- Define CONFIG_CHROMEOS_VBOOT in the Kconfig too
- Correct a bisect build error
Kconfig | 17 +++++++++++++++++ arch/x86/cpu/apollolake/acpi.c | 3 ++- arch/x86/dts/chromebook_coral.dts | 2 +- arch/x86/dts/chromebook_samus.dts | 2 +- arch/x86/include/asm/intel_gnvs.h | 3 --- arch/x86/lib/tpl.c | 2 +- configs/chromebook_coral_defconfig | 3 ++- 7 files changed, 24 insertions(+), 8 deletions(-)
Reviewed-by: Bin Meng bmeng.cn@gmail.com