The uncompressor code port configuration is now handled
by CONFIG_S3C_LOWLEVEL_UART_PORT.
- config DEBUG_REALVIEW_STD_PORT
- bool "RealView Default UART"
- depends on ARCH_REALVIEW
- help
- Say Y here if you want the debug print routines to direct
- their output to the serial port on RealView EB, PB11MP, PBA8
- and PBX platforms.
-
- config DEBUG_REALVIEW_PB1176_PORT
- bool "RealView PB1176 UART"
- depends on MACH_REALVIEW_PB1176
+ config DEBUG_LL_UART_NONE
+ bool "No low-level debugging UART"
help
- Say Y here if you want the debug print routines to direct
- their output to the standard serial port on the RealView
- PB1176 platform.
+ Say Y here if your platform doesn't provide a UART option
+ below. This relies on your platform choosing the right UART
+ definition internally in order for low-level debugging to
+ work.
- config DEBUG_MSM_UART1
- bool "Kernel low-level debugging messages via MSM UART1"
- depends on ARCH_MSM7X00A || ARCH_MSM7X30 || ARCH_QSD8X50
+ config DEBUG_ICEDCC
+ bool "Kernel low-level debugging via EmbeddedICE DCC channel"
help
Say Y here if you want the debug print routines to direct
- their output to the first serial port on MSM devices.
+ their output to the EmbeddedICE macrocell's DCC channel using
+ co-processor 14. This is known to work on the ARM9 style ICE
+ channel and on the XScale with the PEEDI.
- config DEBUG_MSM_UART2
- bool "Kernel low-level debugging messages via MSM UART2"
- depends on ARCH_MSM7X00A || ARCH_MSM7X30 || ARCH_QSD8X50
- help
- Say Y here if you want the debug print routines to direct
- their output to the second serial port on MSM devices.
+ Note that the system will appear to hang during boot if there
+ is nothing connected to read from the DCC.
- config DEBUG_MSM_UART3
- bool "Kernel low-level debugging messages via MSM UART3"
- depends on ARCH_MSM7X00A || ARCH_MSM7X30 || ARCH_QSD8X50
++ config DEBUG_SEMIHOSTING
++ bool "Kernel low-level debug output via semihosting I"
+ help
- Say Y here if you want the debug print routines to direct
- their output to the third serial port on MSM devices.
++ Semihosting enables code running on an ARM target to use
++ the I/O facilities on a host debugger/emulator through a
++ simple SVC calls. The host debugger or emulator must have
++ semihosting enabled for the special svc call to be trapped
++ otherwise the kernel will crash.
+
- config DEBUG_MSM8660_UART
- bool "Kernel low-level debugging messages via MSM 8660 UART"
- depends on ARCH_MSM8X60
- select MSM_HAS_DEBUG_UART_HS
- help
- Say Y here if you want the debug print routines to direct
- their output to the serial port on MSM 8660 devices.
++ This is known to work with OpenOCD, as wellas
++ ARM's Fast Models, or any other controlling environment
++ that implements semihosting.
+
- config DEBUG_MSM8960_UART
- bool "Kernel low-level debugging messages via MSM 8960 UART"
- depends on ARCH_MSM8960
- select MSM_HAS_DEBUG_UART_HS
- help
- Say Y here if you want the debug print routines to direct
- their output to the serial port on MSM 8960 devices.
++ For more details about semihosting, please see
++ chapter 8 of DUI0203I_rvct_developer_guide.pdf from ARM Ltd.
+
endchoice
config EARLY_PRINTK