summaryrefslogtreecommitdiff
path: root/arch/arc/Kconfig
diff options
context:
space:
mode:
authorVineet Gupta <vgupta@synopsys.com>2015-03-09 19:40:09 +0530
committerVineet Gupta <vgupta@synopsys.com>2015-06-19 18:09:27 +0530
commit036b2c5664281e7da5a89c9f742491f30966485f (patch)
treee9e75a0b1eac449927c2bae6a9c6887fdb22bcd3 /arch/arc/Kconfig
parentfd1557923b2e45a7ff4664bd88311d8239d69ca9 (diff)
ARC: explicit'ify uboot support
Signed-off-by: Vineet Gupta <vgupta@synopsys.com>
Diffstat (limited to 'arch/arc/Kconfig')
-rw-r--r--arch/arc/Kconfig12
1 files changed, 12 insertions, 0 deletions
diff --git a/arch/arc/Kconfig b/arch/arc/Kconfig
index 824065a94b37..b52f7eba6765 100644
--- a/arch/arc/Kconfig
+++ b/arch/arc/Kconfig
@@ -388,6 +388,18 @@ config ARC_DBG_TLB_MISS_COUNT
Counts number of I and D TLB Misses and exports them via Debugfs
The counters can be cleared via Debugfs as well
+config ARC_UBOOT_SUPPORT
+ bool "Support uboot arg Handling"
+ default n
+ help
+ ARC Linux by default checks for uboot provided args as pointers to
+ external cmdline or DTB. This however breaks in absence of uboot,
+ when booting from Metaware debugger directly, as the registers are
+ not zeroed out on reset by mdb and/or ARCv2 based cores. The bogus
+ registers look like uboot args to kernel which then chokes.
+ So only enable the uboot arg checking/processing if users are sure
+ of uboot being in play.
+
config ARC_BUILTIN_DTB_NAME
string "Built in DTB"
help