The option ONENAND_BOOT is never set, so remove it. The option
SYS_ONENAND_BOOT was never migrated to Kconfig and any platforms which
supported that have long been removed from the code, so remove the
reference there as well.
Signed-off-by: Tom Rini <tr...@konsulko.com>
---
arch/arm/mach-omap2/omap3/lowlevel_init.S | 4 ++--
boot/Kconfig | 8 --------
2 files changed, 2 insertions(+), 10 deletions(-)
diff --git a/arch/arm/mach-omap2/omap3/lowlevel_init.S
b/arch/arm/mach-omap2/omap3/lowlevel_init.S
index 1ab9472e1987..5541a4714ac0 100644
--- a/arch/arm/mach-omap2/omap3/lowlevel_init.S
+++ b/arch/arm/mach-omap2/omap3/lowlevel_init.S
@@ -176,10 +176,10 @@ ENTRY(lowlevel_init)
ldr sp, SRAM_STACK
str ip, [sp] /* stash ip register */
mov ip, lr /* save link reg across call */
-#if !defined(CONFIG_SYS_NAND_BOOT) && !defined(CONFIG_SYS_ONENAND_BOOT)
+#if !defined(CONFIG_SYS_NAND_BOOT)
/*
* No need to copy/exec the clock code - DPLL adjust already done
- * in NAND/oneNAND Boot.
+ * in NAND Boot.
*/
ldr r1, =SRAM_CLK_CODE
bl cpy_clk_code
diff --git a/boot/Kconfig b/boot/Kconfig
index c09a98c3233c..f101200ba7a5 100644
--- a/boot/Kconfig
+++ b/boot/Kconfig
@@ -1436,14 +1436,6 @@ config NAND_BOOT
booted via NAND flash. This is not a must, some SoCs need this,
some not.
-config ONENAND_BOOT
- bool "Support for booting from ONENAND"
- imply MTD_RAW_NAND
- help
- Enabling this will make a U-Boot binary that is capable of being
- booted via ONENAND. This is not a must, some SoCs need this,
- some not.
-
config QSPI_BOOT
bool "Support for booting from QSPI flash"
help
--
2.43.0
