From 4902e6c5e3be35f5653b304f4b578026473c91a3 Mon Sep 17 00:00:00 2001 From: Tomaz Solc Date: Tue, 5 Mar 2019 09:57:52 +0100 Subject: common: Kconfig: improve help text for DEBUG_LL This adopts the help text used in Linux for the same setting. It clarifies that a build with DEBUG_LL enabled will only work on the system you chose the debug UART for. Signed-off-by: Sascha Hauer --- common/Kconfig | 18 ++++++++++++++---- 1 file changed, 14 insertions(+), 4 deletions(-) (limited to 'common/Kconfig') diff --git a/common/Kconfig b/common/Kconfig index 42769333fe..53052c9cc1 100644 --- a/common/Kconfig +++ b/common/Kconfig @@ -1006,11 +1006,21 @@ config DEBUG_INFO config DEBUG_LL bool depends on HAS_DEBUG_LL - prompt "low level debug messages" + prompt "Low level debug messages (read help)" help - Enable this to get low level debug messages during barebox initialization. - This requires SoC specific support. Most SoCs require the debug UART to be - initialized by a debugger or first stage bootloader. + Enable this to get low level debug messages during barebox + initialization. This is helpful if you are debugging code that + executes before the console is initialized. + + This requires SoC specific support. Most SoCs require the + debug UART to be initialized by a debugger or first stage + bootloader. + + Note that selecting this option will limit barebox to a single + UART definition, as specified below under "low-level debugging + port". Attempting to boot the resulting image on a different + platform *will not work*, so this option should not be enabled + for builds that are intended to be portable. choice prompt "Kernel low-level debugging port" -- cgit v1.2.3