|
@@ -81,41 +81,6 @@ choice
|
|
|
prompt "Kernel low-level debugging port"
|
|
|
depends on DEBUG_LL
|
|
|
|
|
|
- config DEBUG_LL_UART_NONE
|
|
|
- bool "No low-level debugging UART"
|
|
|
- help
|
|
|
- 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_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 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.
|
|
|
-
|
|
|
- Note that the system will appear to hang during boot if there
|
|
|
- is nothing connected to read from the DCC.
|
|
|
-
|
|
|
- config DEBUG_SEMIHOSTING
|
|
|
- bool "Kernel low-level debug output via semihosting I"
|
|
|
- help
|
|
|
- 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.
|
|
|
-
|
|
|
- This is known to work with OpenOCD, as wellas
|
|
|
- ARM's Fast Models, or any other controlling environment
|
|
|
- that implements semihosting.
|
|
|
-
|
|
|
- For more details about semihosting, please see
|
|
|
- chapter 8 of DUI0203I_rvct_developer_guide.pdf from ARM Ltd.
|
|
|
-
|
|
|
config AT91_DEBUG_LL_DBGU0
|
|
|
bool "Kernel low-level debugging on rm9200, 9260/9g20, 9261/9g10 and 9rl"
|
|
|
depends on HAVE_AT91_DBGU0
|
|
@@ -124,20 +89,6 @@ choice
|
|
|
bool "Kernel low-level debugging on 9263, 9g45 and cap9"
|
|
|
depends on HAVE_AT91_DBGU1
|
|
|
|
|
|
- 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_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_CLPS711X_UART1
|
|
|
bool "Kernel low-level debugging messages via UART1"
|
|
|
depends on ARCH_CLPS711X
|
|
@@ -152,6 +103,20 @@ choice
|
|
|
Say Y here if you want the debug print routines to direct
|
|
|
their output to the second serial port on these devices.
|
|
|
|
|
|
+ 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_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_HIGHBANK_UART
|
|
|
bool "Kernel low-level debugging messages via Highbank UART"
|
|
|
depends on ARCH_HIGHBANK
|
|
@@ -222,6 +187,59 @@ choice
|
|
|
Say Y here if you want kernel low-level debugging support
|
|
|
on i.MX6Q.
|
|
|
|
|
|
+ config DEBUG_MSM_UART1
|
|
|
+ bool "Kernel low-level debugging messages via MSM UART1"
|
|
|
+ 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 first serial port on MSM devices.
|
|
|
+
|
|
|
+ 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.
|
|
|
+
|
|
|
+ config DEBUG_MSM_UART3
|
|
|
+ bool "Kernel low-level debugging messages via MSM UART3"
|
|
|
+ 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 third serial port on MSM devices.
|
|
|
+
|
|
|
+ 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.
|
|
|
+
|
|
|
+ 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.
|
|
|
+
|
|
|
+ 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
|
|
|
+ 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.
|
|
|
+
|
|
|
config DEBUG_S3C_UART0
|
|
|
depends on PLAT_SAMSUNG
|
|
|
bool "Use S3C UART 0 for low-level debug"
|
|
@@ -255,58 +273,40 @@ choice
|
|
|
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
|
|
|
|