1menu "Kernel hacking"
2 3source "lib/Kconfig.debug"
4 5config STRICT_DEVMEM
6 bool "Filter access to /dev/mem"
7 depends on MMU
8 ---help---
9 If this option is disabled, you allow userspace (root) access to all
10 of memory, including kernel and userspace memory. Accidental
11 access to this is obviously disastrous, but specific access can
12 be used by people debugging the kernel.
13 14 If this option is switched on, the /dev/mem file only allows
15 userspace access to memory mapped peripherals.
16 17 If in doubt, say Y.
18 19config EARLY_PRINTK
20 def_bool DEBUG_OCD
21 help
22 Write kernel log output directly into the ocd or to a serial port.
23 24 This is useful for kernel debugging when your machine crashes very
25 early before the console code is initialized. For normal operation
26 it is not recommended because it looks ugly and doesn't cooperate
27 with klogd/syslogd or the X server. You should normally N here,
28 unless you want to debug such a crash.
29 30# These options are only for real kernel hackers who want to get their hands dirty.
31config DEBUG_LL
32 bool "Kernel low-level debugging functions"
33 depends on DEBUG_KERNEL
34 help
35 Say Y here to include definitions of printascii, printch, printhex
36 in the kernel. This is helpful if you are debugging code that
37 executes before the console is initialized.
38 39config DEBUG_OCD
40 bool "Kernel low-level debugging via On-Chip-Debugger"
41 depends on DEBUG_LL
42 default y
43 help
44 Say Y here if you want the debug print routines to direct their
45 output to the UniCore On-Chip-Debugger channel using CP #1.
46 47endmenu
48