menu "Kernel hacking" source "lib/Kconfig.debug" config ARM_PTDUMP	bool "Export kernel pagetable layout to userspace via debugfs"	depends on DEBUG_KERNEL	depends on MMU	select DEBUG_FS	---help---	  Say Y here if you want to show the kernel pagetable layout in a	  debugfs file. This information is only useful for kernel developers	  who are working in architecture specific areas of the kernel.	  It is probably not a good idea to enable this feature in a production	  kernel.	  If in doubt, say "N" config STRICT_DEVMEM	bool "Filter access to /dev/mem"	depends on MMU	---help---	  If this option is disabled, you allow userspace (root) access to all	  of memory, including kernel and userspace memory. Accidental	  access to this is obviously disastrous, but specific access can	  be used by people debugging the kernel. 	  If this option is switched on, the /dev/mem file only allows	  userspace access to memory mapped peripherals.           If in doubt, say Y. # RMK wants arm kernels compiled with frame pointers or stack unwinding.# If you know what you are doing and are willing to live without stack# traces, you can get a slightly smaller kernel by setting this option to# n, but then RMK will have to kill you ;).config FRAME_POINTER	bool	depends on !THUMB2_KERNEL	default y if !ARM_UNWIND || FUNCTION_GRAPH_TRACER	help	  If you say N here, the resulting kernel will be slightly smaller and	  faster. However, if neither FRAME_POINTER nor ARM_UNWIND are enabled,	  when a problem occurs with the kernel, the information that is	  reported is severely limited. config ARM_UNWIND	bool "Enable stack unwinding support (EXPERIMENTAL)"	depends on AEABI	default y	help	  This option enables stack unwinding support in the kernel	  using the information automatically generated by the	  compiler. The resulting kernel image is slightly bigger but	  the performance is not affected. Currently, this feature	  only works with EABI compilers. If unsure say Y. config OLD_MCOUNT	bool	depends on FUNCTION_TRACER && FRAME_POINTER	default y config DEBUG_USER	bool "Verbose user fault messages"	help	  When a user program crashes due to an exception, the kernel can	  print a brief message explaining what the problem was. This is	  sometimes helpful for debugging but serves no purpose on a	  production system. Most people should say N here. 	  In addition, you need to pass user_debug=N on the kernel command	  line to enable this feature.  N consists of the sum of: 	      1 - undefined instruction events	      2 - system calls	      4 - invalid data aborts	      8 - SIGSEGV faults	     16 - SIGBUS faults # These options are only for real kernel hackers who want to get their hands dirty.config DEBUG_LL	bool "Kernel low-level debugging functions (read help!)"	depends on DEBUG_KERNEL	help	  Say Y here to include definitions of printascii, printch, printhex	  in the kernel.  This is helpful if you are debugging code that	  executes before the console is initialized. 	  Note that selecting this option will limit the kernel to a single	  UART definition, as specified below. Attempting to boot the kernel	  image on a different platform *will not work*, so this option should	  not be enabled for kernels that are intended to be portable. choice	prompt "Kernel low-level debugging port"	depends on DEBUG_LL 	config DEBUG_ALPINE_UART0		bool "Kernel low-level debugging messages via Alpine UART0"		depends on ARCH_ALPINE		select DEBUG_UART_8250		help		  Say Y here if you want kernel low-level debugging support		  on Alpine based platforms. 	config DEBUG_ASM9260_UART		bool "Kernel low-level debugging via asm9260 UART"		depends on MACH_ASM9260		help		  Say Y here if you want the debug print routines to direct		  their output to an UART or USART port on asm9260 based		  machines. 		    DEBUG_UART_PHYS | DEBUG_UART_VIRT 		    0x80000000      | 0xf0000000     | UART0		    0x80004000      | 0xf0004000     | UART1		    0x80008000      | 0xf0008000     | UART2		    0x8000c000      | 0xf000c000     | UART3		    0x80010000      | 0xf0010000     | UART4		    0x80014000      | 0xf0014000     | UART5		    0x80018000      | 0xf0018000     | UART6		    0x8001c000      | 0xf001c000     | UART7		    0x80020000      | 0xf0020000     | UART8		    0x80024000      | 0xf0024000     | UART9 	config AT91_DEBUG_LL_DBGU0		bool "Kernel low-level debugging on rm9200, 9260/9g20, 9261/9g10, 9rl, 9x5, 9n12"		select DEBUG_AT91_UART		depends on ARCH_AT91		depends on SOC_AT91RM9200 || SOC_AT91SAM9 	config AT91_DEBUG_LL_DBGU1		bool "Kernel low-level debugging on 9263, 9g45 and sama5d3"		select DEBUG_AT91_UART		depends on ARCH_AT91		depends on SOC_AT91SAM9 || SOC_SAMA5 	config AT91_DEBUG_LL_DBGU2		bool "Kernel low-level debugging on sama5d4"		select DEBUG_AT91_UART		depends on ARCH_AT91		depends on SOC_SAMA5 	config DEBUG_BCM2835		bool "Kernel low-level debugging on BCM2835 PL011 UART"		depends on ARCH_BCM2835		select DEBUG_UART_PL01X 	config DEBUG_BCM_5301X		bool "Kernel low-level debugging on BCM5301X UART1"		depends on ARCH_BCM_5301X		select DEBUG_UART_8250 	config DEBUG_BCM_KONA_UART		bool "Kernel low-level debugging messages via BCM KONA UART"		depends on ARCH_BCM_MOBILE		select DEBUG_UART_8250		help		  Say Y here if you want kernel low-level debugging support		  on Broadcom SoC platforms.		  This low level debug works for Broadcom		  mobile SoCs in the Kona family of chips (e.g. bcm28155,		  bcm11351, etc...) 	config DEBUG_BCM63XX		bool "Kernel low-level debugging on BCM63XX UART"		depends on ARCH_BCM_63XX		select DEBUG_UART_BCM63XX 	config DEBUG_BERLIN_UART		bool "Marvell Berlin SoC Debug UART"		depends on ARCH_BERLIN		select DEBUG_UART_8250		help		  Say Y here if you want kernel low-level debugging support		  on Marvell Berlin SoC based platforms. 	config DEBUG_BRCMSTB_UART		bool "Use BRCMSTB UART for low-level debug"		depends on ARCH_BRCMSTB		select DEBUG_UART_8250		help		  Say Y here if you want the debug print routines to direct		  their output to the first serial port on these devices. 		  If you have a Broadcom STB chip and would like early print		  messages to appear over the UART, select this option. 	config DEBUG_CLPS711X_UART1		bool "Kernel low-level debugging messages via UART1"		depends on ARCH_CLPS711X		help		  Say Y here if you want the debug print routines to direct		  their output to the first serial port on these devices. 	config DEBUG_CLPS711X_UART2		bool "Kernel low-level debugging messages via UART2"		depends on ARCH_CLPS711X		help		  Say Y here if you want the debug print routines to direct		  their output to the second serial port on these devices. 	config DEBUG_CNS3XXX		bool "Kernel Kernel low-level debugging on Cavium Networks CNS3xxx"		depends on ARCH_CNS3XXX		select DEBUG_UART_8250		help		  Say Y here if you want the debug print routines to direct                  their output to the CNS3xxx UART0. 	config DEBUG_DAVINCI_DA8XX_UART1		bool "Kernel low-level debugging on DaVinci DA8XX using UART1"		depends on ARCH_DAVINCI_DA8XX		select DEBUG_UART_8250		help		  Say Y here if you want the debug print routines to direct		  their output to UART1 serial port on DaVinci DA8XX devices. 	config DEBUG_DAVINCI_DA8XX_UART2		bool "Kernel low-level debugging on DaVinci DA8XX using UART2"		depends on ARCH_DAVINCI_DA8XX		select DEBUG_UART_8250		help		  Say Y here if you want the debug print routines to direct		  their output to UART2 serial port on DaVinci DA8XX devices. 	config DEBUG_DAVINCI_DMx_UART0		bool "Kernel low-level debugging on DaVinci DMx using UART0"		depends on ARCH_DAVINCI_DMx		select DEBUG_UART_8250		help		  Say Y here if you want the debug print routines to direct		  their output to UART0 serial port on DaVinci DMx devices. 	config DEBUG_ZYNQ_UART0		bool "Kernel low-level debugging on Xilinx Zynq using UART0"		depends on ARCH_ZYNQ		help		  Say Y here if you want the debug print routines to direct		  their output to UART0 on the Zynq platform. 	config DEBUG_ZYNQ_UART1		bool "Kernel low-level debugging on Xilinx Zynq using UART1"		depends on ARCH_ZYNQ		help		  Say Y here if you want the debug print routines to direct		  their output to UART1 on the Zynq platform. 		  If you have a ZC702 board and want early boot messages to		  appear on the USB serial adaptor, select this option. 	config DEBUG_DC21285_PORT		bool "Kernel low-level debugging messages via footbridge serial port"		depends on FOOTBRIDGE		help		  Say Y here if you want the debug print routines to direct		  their output to the serial port in the DC21285 (Footbridge). 	config DEBUG_DIGICOLOR_UA0		bool "Kernel low-level debugging messages via Digicolor UA0"		depends on ARCH_DIGICOLOR		help		  Say Y here if you want the debug print routines to direct		  their output to the UA0 serial port in the CX92755. 	config DEBUG_FOOTBRIDGE_COM1		bool "Kernel low-level debugging messages via footbridge 8250 at PCI COM1"		depends on FOOTBRIDGE		help		  Say Y here if you want the debug print routines to direct		  their output to the 8250 at PCI COM1. 	config DEBUG_HI3620_UART		bool "Hisilicon HI3620 Debug UART"		depends on ARCH_HI3xxx		select DEBUG_UART_PL01X		help		  Say Y here if you want kernel low-level debugging support		  on HI3620 UART. 	config DEBUG_HI3716_UART		bool "Hisilicon Hi3716 Debug UART"		depends on ARCH_HI3xxx		select DEBUG_UART_PL01X		help		  Say Y here if you want kernel low-level debugging support		  on HI3716 UART. 	config DEBUG_HIGHBANK_UART		bool "Kernel low-level debugging messages via Highbank UART"		depends on ARCH_HIGHBANK		select DEBUG_UART_PL01X		help		  Say Y here if you want the debug print routines to direct		  their output to the UART on Highbank based devices. 	config DEBUG_HIP01_UART		bool "Hisilicon Hip01 Debug UART"		depends on ARCH_HIP01		select DEBUG_UART_8250		help		  Say Y here if you want kernel low-level debugging support		  on HIP01 UART. 	config DEBUG_HIP04_UART		bool "Hisilicon HiP04 Debug UART"		depends on ARCH_HIP04		select DEBUG_UART_8250		help		  Say Y here if you want kernel low-level debugging support		  on HIP04 UART. 	config DEBUG_HIX5HD2_UART		bool "Hisilicon Hix5hd2 Debug UART"		depends on ARCH_HIX5HD2		select DEBUG_UART_PL01X		help		  Say Y here if you want kernel low-level debugging support		  on Hix5hd2 UART. 	config DEBUG_IMX1_UART		bool "i.MX1 Debug UART"		depends on SOC_IMX1		help		  Say Y here if you want kernel low-level debugging support		  on i.MX1. 	config DEBUG_IMX23_UART		bool "i.MX23 Debug UART"		depends on SOC_IMX23		select DEBUG_UART_PL01X		help		  Say Y here if you want kernel low-level debugging support		  on i.MX23. 	config DEBUG_IMX25_UART		bool "i.MX25 Debug UART"		depends on SOC_IMX25		help		  Say Y here if you want kernel low-level debugging support		  on i.MX25. 	config DEBUG_IMX21_IMX27_UART		bool "i.MX21 and i.MX27 Debug UART"		depends on SOC_IMX21 || SOC_IMX27		help		  Say Y here if you want kernel low-level debugging support		  on i.MX21 or i.MX27. 	config DEBUG_IMX28_UART		bool "i.MX28 Debug UART"		depends on SOC_IMX28		select DEBUG_UART_PL01X		help		  Say Y here if you want kernel low-level debugging support		  on i.MX28. 	config DEBUG_IMX31_UART		bool "i.MX31 Debug UART"		depends on SOC_IMX31		help		  Say Y here if you want kernel low-level debugging support		  on i.MX31. 	config DEBUG_IMX35_UART		bool "i.MX35 Debug UART"		depends on SOC_IMX35		help		  Say Y here if you want kernel low-level debugging support		  on i.MX35. 	config DEBUG_IMX50_UART		bool "i.MX50 Debug UART"		depends on SOC_IMX50		help		  Say Y here if you want kernel low-level debugging support		  on i.MX50. 	config DEBUG_IMX51_UART		bool "i.MX51 Debug UART"		depends on SOC_IMX51		help		  Say Y here if you want kernel low-level debugging support		  on i.MX51. 	config DEBUG_IMX53_UART		bool "i.MX53 Debug UART"		depends on SOC_IMX53		help		  Say Y here if you want kernel low-level debugging support		  on i.MX53. 	config DEBUG_IMX6Q_UART		bool "i.MX6Q/DL Debug UART"		depends on SOC_IMX6Q		help		  Say Y here if you want kernel low-level debugging support		  on i.MX6Q/DL. 	config DEBUG_IMX6SL_UART		bool "i.MX6SL Debug UART"		depends on SOC_IMX6SL		help		  Say Y here if you want kernel low-level debugging support		  on i.MX6SL. 	config DEBUG_IMX6SX_UART		bool "i.MX6SX Debug UART"		depends on SOC_IMX6SX		help		  Say Y here if you want kernel low-level debugging support		  on i.MX6SX. 	config DEBUG_IMX7D_UART		bool "i.MX7D Debug UART"		depends on SOC_IMX7D		help		  Say Y here if you want kernel low-level debugging support		  on i.MX7D. 	config DEBUG_KEYSTONE_UART0		bool "Kernel low-level debugging on KEYSTONE2 using UART0"		depends on ARCH_KEYSTONE		select DEBUG_UART_8250		help		  Say Y here if you want the debug print routines to direct		  their output to UART0 serial port on KEYSTONE2 devices. 	config DEBUG_KEYSTONE_UART1		bool "Kernel low-level debugging on KEYSTONE2 using UART1"		depends on ARCH_KEYSTONE		select DEBUG_UART_8250		help		  Say Y here if you want the debug print routines to direct		  their output to UART1 serial port on KEYSTONE2 devices. 	config DEBUG_KS8695_UART		bool "KS8695 Debug UART"		depends on ARCH_KS8695		help		  Say Y here if you want kernel low-level debugging support		  on KS8695. 	config DEBUG_LPC18XX_UART0		bool "Kernel low-level debugging via LPC18xx/43xx UART0"		depends on ARCH_LPC18XX		select DEBUG_UART_8250		help		  Say Y here if you want kernel low-level debugging support		  on NXP LPC18xx/43xx UART0. 	config DEBUG_MESON_UARTAO		bool "Kernel low-level debugging via Meson6 UARTAO"		depends on ARCH_MESON		help		  Say Y here if you want kernel low-lever debugging support		  on Amlogic Meson6 based platforms on the UARTAO. 	config DEBUG_MMP_UART2		bool "Kernel low-level debugging message via MMP UART2"		depends on ARCH_MMP		select DEBUG_UART_8250		help		  Say Y here if you want kernel low-level debugging support		  on MMP UART2. 	config DEBUG_MMP_UART3		bool "Kernel low-level debugging message via MMP UART3"		depends on ARCH_MMP		select DEBUG_UART_8250		help		  Say Y here if you want kernel low-level debugging support		  on MMP UART3. 	config DEBUG_QCOM_UARTDM		bool "Kernel low-level debugging messages via QCOM UARTDM"		depends on ARCH_QCOM		help		  Say Y here if you want the debug print routines to direct		  their output to the serial port on Qualcomm devices. 		  ARCH      DEBUG_UART_PHYS   DEBUG_UART_VIRT		  APQ8064   0x16640000        0xf0040000		  APQ8084   0xf995e000        0xfa75e000		  MSM8X60   0x19c40000        0xf0040000		  MSM8960   0x16440000        0xf0040000		  MSM8974   0xf991e000        0xfa71e000 		  Please adjust DEBUG_UART_PHYS and DEBUG_UART_BASE configuration		  options based on your needs. 	config DEBUG_MVEBU_UART0		bool "Kernel low-level debugging messages via MVEBU UART0 (old bootloaders)"		depends on ARCH_MVEBU		select DEBUG_UART_8250		help		  Say Y here if you want kernel low-level debugging support		  on MVEBU based platforms on UART0. 		  This option should be used with the old bootloaders

Lines 1–500 of 1649. Load more