qi-hardware/openwrt-xburst
1
0
Fork 0
mirror of git://projects.qi-hardware.com/openwrt-xburst.git synced 2025-04-21 12:27:27 +03:00
Code Activity

incomplete Gumstix support

Browse Source 
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@10955 3c298f89-4303-0410-b956-a3cf2f4a3e73
This commit is contained in:
kaloz
2008-04-27 16:56:19 +00:00
parent 1984be2194
commit c886d2690d
47 changed files with 19222 additions and 364 deletions
Download Patch File Download Diff File Expand all files Collapse all files

38
target/linux/pxa/patches-2.6.21/032-misalignment-handling.patch Normal file
View File

@@ -0,0 +1,38 @@
Change the default alingment handling to not be silent failure
Index: linux-2.6.21gum/arch/arm/mm/alignment.c
===================================================================
--- linux-2.6.21gum.orig/arch/arm/mm/alignment.c
+++ linux-2.6.21gum/arch/arm/mm/alignment.c
@@ -797,6 +797,8 @@ static int __init alignment_init(void)
res->write_proc = proc_alignment_write;
#endif
+ ai_usermode = CONFIG_ALIGNMENT_HANDLING;
+
hook_fault_code(1, do_alignment, SIGILL, "alignment exception");
hook_fault_code(3, do_alignment, SIGILL, "alignment exception");
Index: linux-2.6.21gum/arch/arm/Kconfig
===================================================================
--- linux-2.6.21gum.orig/arch/arm/Kconfig
+++ linux-2.6.21gum/arch/arm/Kconfig
@@ -709,6 +709,19 @@ config ALIGNMENT_TRAP
correct operation of some network protocols. With an IP-only
configuration it is safe to say N, otherwise say Y.
+config ALIGNMENT_HANDLING
+ hex "Userspace alignment trap handling"
+ default "0x3"
+ depends on ALIGNMENT_TRAP
+ help
+ How should we handle alignment errors in userspace by default? This is a bitfield where:
+ 0 - silently ignore alignment errors (will lead to unexpected results)
+ 1 - report alignment errors through printk (will lead to unexpected results, but you'll know about them)
+ 2 - fix the alignment and make things work properly (performance degradation for un-aligned code)
+ 4 - raise SIGBUS on alignment traps
+ A good number to choose is probably either 3 (work slowly but log message) or 5 (log message and SIGBUS).
+ You can change the behavior at runtime through /proc/cpu/alignment if you have PROC_FS enabled.
+
endmenu
menu "Boot options"