Messages in this thread Patch in this message | | | Date | Fri, 6 Jan 2006 16:29:35 GMT | From | David Howells <> | Subject | [PATCH 3/17] FRV: Drop unsupported debugging features |
| |
The attached patch drops support for debugging features that aren't supported on FRV:
(*) EARLY_PRINTK
The on-chip UARTs are set up early enough that this isn't required, and VGA support isn't available. There's also a gdbstub available.
(*) DEBUG_PAGEALLOC
This can't be easily be done since we use huge static mappings to cover the kernel, not pages.
Signed-Off-By: David Howells <dhowells@redhat.com> --- warthog>diffstat -p1 frv-debugging-2615.diff arch/frv/Kconfig.debug | 22 ---------------------- 1 files changed, 22 deletions(-)
diff -uNrp /warthog/kernels/linux-2.6.15/arch/frv/Kconfig.debug linux-2.6.15-frv/arch/frv/Kconfig.debug --- /warthog/kernels/linux-2.6.15/arch/frv/Kconfig.debug 2005-06-22 13:51:25.000000000 +0100 +++ linux-2.6.15-frv/arch/frv/Kconfig.debug 2006-01-06 14:43:43.000000000 +0000 @@ -2,32 +2,10 @@ menu "Kernel hacking" source "lib/Kconfig.debug" -config EARLY_PRINTK - bool "Early printk" - depends on EMBEDDED && DEBUG_KERNEL - default n - help - Write kernel log output directly into the VGA buffer or to a serial - port. - - This is useful for kernel debugging when your machine crashes very - early before the console code is initialized. For normal operation - it is not recommended because it looks ugly and doesn't cooperate - with klogd/syslogd or the X server. You should normally N here, - unless you want to debug such a crash. - config DEBUG_STACKOVERFLOW bool "Check for stack overflows" depends on DEBUG_KERNEL -config DEBUG_PAGEALLOC - bool "Page alloc debugging" - depends on DEBUG_KERNEL - help - Unmap pages from the kernel linear mapping after free_pages(). - This results in a large slowdown, but helps to find certain types - of memory corruptions. - config GDBSTUB bool "Remote GDB kernel debugging" depends on DEBUG_KERNEL - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |