blob: f075bbe1d46f4ec1084f40ddd68396c39515e5ff [file] [log] [blame]
GuanXuetao790edb62011-02-26 18:24:56 +08001menu "Kernel hacking"
2
3source "lib/Kconfig.debug"
4
GuanXuetao790edb62011-02-26 18:24:56 +08005config EARLY_PRINTK
6 def_bool DEBUG_OCD
7 help
8 Write kernel log output directly into the ocd or to a serial port.
9
10 This is useful for kernel debugging when your machine crashes very
11 early before the console code is initialized. For normal operation
12 it is not recommended because it looks ugly and doesn't cooperate
13 with klogd/syslogd or the X server. You should normally N here,
14 unless you want to debug such a crash.
15
GuanXuetao790edb62011-02-26 18:24:56 +080016# These options are only for real kernel hackers who want to get their hands dirty.
17config DEBUG_LL
18 bool "Kernel low-level debugging functions"
19 depends on DEBUG_KERNEL
20 help
21 Say Y here to include definitions of printascii, printch, printhex
22 in the kernel. This is helpful if you are debugging code that
23 executes before the console is initialized.
24
25config DEBUG_OCD
26 bool "Kernel low-level debugging via On-Chip-Debugger"
27 depends on DEBUG_LL
28 default y
29 help
30 Say Y here if you want the debug print routines to direct their
31 output to the UniCore On-Chip-Debugger channel using CP #1.
32
GuanXuetao790edb62011-02-26 18:24:56 +080033endmenu