1menu "Kernel hacking" 2 3source "lib/Kconfig.debug" 4 5# RMK wants arm kernels compiled with frame pointers so hardwire this to y. 6# If you know what you are doing and are willing to live without stack 7# traces, you can get a slightly smaller kernel by setting this option to 8# n, but then RMK will have to kill you ;). 9config FRAME_POINTER 10 bool 11 default y 12 help 13 If you say N here, the resulting kernel will be slightly smaller and 14 faster. However, when a problem occurs with the kernel, the 15 information that is reported is severely limited. Most people 16 should say Y here. 17 18config DEBUG_USER 19 bool "Verbose user fault messages" 20 help 21 When a user program crashes due to an exception, the kernel can 22 print a brief message explaining what the problem was. This is 23 sometimes helpful for debugging but serves no purpose on a 24 production system. Most people should say N here. 25 26 In addition, you need to pass user_debug=N on the kernel command 27 line to enable this feature. N consists of the sum of: 28 29 1 - undefined instruction events 30 2 - system calls 31 4 - invalid data aborts 32 8 - SIGSEGV faults 33 16 - SIGBUS faults 34 35config DEBUG_ERRORS 36 bool "Verbose kernel error messages" 37 depends on DEBUG_KERNEL 38 help 39 This option controls verbose debugging information which can be 40 printed when the kernel detects an internal error. This debugging 41 information is useful to kernel hackers when tracking down problems, 42 but mostly meaningless to other people. It's safe to say Y unless 43 you are concerned with the code size or don't want to see these 44 messages. 45 46 47# These options are only for real kernel hackers who want to get their hands dirty. 48config DEBUG_LL 49 bool "Kernel low-level debugging functions" 50 depends on DEBUG_KERNEL 51 help 52 Say Y here to include definitions of printascii, printch, printhex 53 in the kernel. This is helpful if you are debugging code that 54 executes before the console is initialized. 55 56config DEBUG_ICEDCC 57 bool "Kernel low-level debugging via EmbeddedICE DCC channel" 58 depends on DEBUG_LL 59 help 60 Say Y here if you want the debug print routines to direct their 61 output to the EmbeddedICE macrocell's DCC channel using 62 co-processor 14. This is known to work on the ARM9 style ICE 63 channel. 64 65 It does include a timeout to ensure that the system does not 66 totally freeze when there is nothing connected to read. 67 68config DEBUG_DC21285_PORT 69 bool "Kernel low-level debugging messages via footbridge serial port" 70 depends on DEBUG_LL && FOOTBRIDGE 71 help 72 Say Y here if you want the debug print routines to direct their 73 output to the serial port in the DC21285 (Footbridge). Saying N 74 will cause the debug messages to appear on the first 16550 75 serial port. 76 77config DEBUG_CLPS711X_UART2 78 bool "Kernel low-level debugging messages via UART2" 79 depends on DEBUG_LL && ARCH_CLPS711X 80 help 81 Say Y here if you want the debug print routines to direct their 82 output to the second serial port on these devices. Saying N will 83 cause the debug messages to appear on the first serial port. 84 85config DEBUG_S3C_PORT 86 depends on DEBUG_LL && PLAT_S3C 87 bool "Kernel low-level debugging messages via S3C UART" 88 help 89 Say Y here if you want debug print routines to go to one of the 90 S3C internal UARTs. The chosen UART must have been configured 91 before it is used. 92 93config DEBUG_S3C_UART 94 depends on PLAT_S3C 95 int "S3C UART to use for low-level debug" 96 default "0" 97 help 98 Choice for UART for kernel low-level using S3C UARTS, 99 should be between zero and two. The port must have been 100 initialised by the boot-loader before use. 101 102 The uncompressor code port configuration is now handled 103 by CONFIG_S3C_LOWLEVEL_UART_PORT. 104 105endmenu 106