UPSTREAM: GDB_WAIT: Clarify Kconfig description

The user has to know in which stage gdb is waiting to be able to
use symbolic debugging.

BUG=none
BRANCH=none
TEST=none

Change-Id: Ib350d5305384b42d09b0660f15c9708537d29590
Signed-off-by: Patrick Georgi <pgeorgi@chromium.org>
Original-Commit-Id: 7d234f2e69
Original-Change-Id: Ia992e7a2077b92c45546ae56c5fb648775f8f63b
Original-Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@no-log.org>
Original-Reviewed-on: https://review.coreboot.org/12709
Original-Tested-by: build bot (Jenkins)
Original-Reviewed-by: Jonathan Neuschfer <j.neuschaefer@gmx.net>
Original-Reviewed-by: Nico Huber <nico.h@gmx.de>
Reviewed-on: https://chromium-review.googlesource.com/455818
This commit is contained in:
Denis 'GNUtoo' Carikli 2015-12-10 21:58:52 +01:00 committed by chrome-bot
commit 8d8b2911c8

View file

@ -673,11 +673,12 @@ config GDB_STUB
See src/arch/x86/lib/c_start.S for details.
config GDB_WAIT
bool "Wait for a GDB connection"
bool "Wait for a GDB connection in the ramstage"
default n
depends on GDB_STUB
help
If enabled, coreboot will wait for a GDB connection.
If enabled, coreboot will wait for a GDB connection in the ramstage.
config FATAL_ASSERTS
bool "Halt when hitting a BUG() or assertion error"