summaryrefslogtreecommitdiff
path: root/configs/bcm11130_defconfig
diff options
context:
space:
mode:
authorMasahiro Yamada <yamada.masahiro@socionext.com>2016-06-20 17:33:39 +0900
committerTom Rini <trini@konsulko.com>2016-06-20 05:19:09 -0400
commit41598c82513672b1052c88ce816d98467345141f (patch)
treed5becad1d40063d826dcd52e4a908363e9e43231 /configs/bcm11130_defconfig
parent2313d48445e59f063ec9a3b4940fe8252737db76 (diff)
downloadu-boot-41598c82513672b1052c88ce816d98467345141f.tar.gz
autoboot: add CONFIG_AUTOBOOT to allow to not compile autoboot.c
Since commit bb597c0eeb7e ("common: bootdelay: move CONFIG_BOOTDELAY into a Kconfig option"), CONFIG_BOOTDELAY is defined for all boards. Prior to that commit, it was allowed to unset CONFIG_BOOTDELAY to not compile common/autoboot.c, as described in common/Makefile: # This option is not just y/n - it can have a numeric value ifdef CONFIG_BOOTDELAY obj-y += autoboot.o endif It was a bit odd to enable/disable code with an integer type option, but it was how this option worked before that commit, and several boards actually unset it to opt out of the autoboot feature. This commit adds a new bool option, CONFIG_AUTOBOOT, and makes CONFIG_BOOTDELAY depend on it. I chose "default y" for this option because most boards use the autoboot. I added "# CONFIG_AUTOBOOT is not set" for the boards that had not set CONFIG_BOOTDELAY prior to the bad commit. Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
Diffstat (limited to 'configs/bcm11130_defconfig')
-rw-r--r--configs/bcm11130_defconfig1
1 files changed, 1 insertions, 0 deletions
diff --git a/configs/bcm11130_defconfig b/configs/bcm11130_defconfig
index 2716868a31..d2a3b7395b 100644
--- a/configs/bcm11130_defconfig
+++ b/configs/bcm11130_defconfig
@@ -2,6 +2,7 @@ CONFIG_ARM=y
CONFIG_TARGET_BCM28155_AP=y
CONFIG_SYS_EXTRA_OPTIONS="SYS_MMC_ENV_DEV=0"
CONFIG_HUSH_PARSER=y
+# CONFIG_AUTOBOOT is not set
CONFIG_CMD_BOOTZ=y
# CONFIG_CMD_IMLS is not set
CONFIG_CMD_ASKENV=y