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
30config DEBUG_STACK_USAGE
31	bool "Enable stack utilization instrumentation"
32	depends on DEBUG_KERNEL
33	help
34	  Enables the display of the minimum amount of free stack which each
35	  task has ever had available in the sysrq-T output.
36
37# These options are only for real kernel hackers who want to get their hands dirty.
38config DEBUG_LL
39	bool "Kernel low-level debugging functions"
40	depends on DEBUG_KERNEL
41	help
42	  Say Y here to include definitions of printascii, printch, printhex
43	  in the kernel.  This is helpful if you are debugging code that
44	  executes before the console is initialized.
45
46config DEBUG_OCD
47	bool "Kernel low-level debugging via On-Chip-Debugger"
48	depends on DEBUG_LL
49	default y
50	help
51	  Say Y here if you want the debug print routines to direct their
52	  output to the UniCore On-Chip-Debugger channel using CP #1.
53
54config DEBUG_OCD_BREAKPOINT
55	bool "Breakpoint support via On-Chip-Debugger"
56	depends on DEBUG_OCD
57
58config DEBUG_UART
59	int "Kernel low-level debugging messages via serial port"
60	depends on DEBUG_LL
61	range 0 1
62	default "0"
63	help
64	  Choice for UART for kernel low-level using PKUnity UARTS,
65	  should be between zero and one. The port must have been
66	  initialised by the boot-loader before use.
67
68endmenu
69