summaryrefslogtreecommitdiffstats
path: root/configs
diff options
context:
space:
mode:
authorChristian Walter <christian.walter@9elements.com>2019-07-29 10:39:15 +0200
committerPhilipp Deppenwiese <zaolin.daisuki@gmail.com>2019-07-29 18:26:20 +0000
commit04f995150f1cf49ce4b9a999095f1ebf8fe28911 (patch)
treec2d5cb19be69f3546de456d62790b334121ba9d0 /configs
parent9429b70f911f0ebab92a236234974bf0c8e6b565 (diff)
downloadcoreboot-04f995150f1cf49ce4b9a999095f1ebf8fe28911.tar.gz
coreboot-04f995150f1cf49ce4b9a999095f1ebf8fe28911.tar.bz2
coreboot-04f995150f1cf49ce4b9a999095f1ebf8fe28911.zip
configs: Add test-build for up squared with vboot enabled
It would be useful if we have at least one "new" board on which we actually built vboot, in order to notice if something breaks. Change-Id: I16c7867e3f0f4e1f2e6ae3918c30789e39881b85 Signed-off-by: Christian Walter <christian.walter@9elements.com> Reviewed-on: https://review.coreboot.org/c/coreboot/+/34609 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Patrick Rudolph <siro@das-labor.org> Reviewed-by: Philipp Deppenwiese <zaolin.daisuki@gmail.com>
Diffstat (limited to 'configs')
-rw-r--r--configs/config.up_squared.vboot2
1 files changed, 2 insertions, 0 deletions
diff --git a/configs/config.up_squared.vboot b/configs/config.up_squared.vboot
new file mode 100644
index 000000000000..130c02f6ec9e
--- /dev/null
+++ b/configs/config.up_squared.vboot
@@ -0,0 +1,2 @@
+CONFIG_VENDOR_UP=y
+CONFIG_VBOOT=y