summaryrefslogtreecommitdiff
path: root/arch/arm/mach-omap1/include
AgeCommit message (Collapse)Author
2009-10-20omap: headers: Create headers necessary for compile under mach-omap1 and ↵Tony Lindgren
mach-omap2 Create the headers needed for compiling under mach-omap1/include/mach and mach-omap2/include/mach. This was done with the following script: #!/bin/bash mach_files="clkdev.h gpio.h hardware.h io.h irqs.h memory.h \ smp.h system.h timex.h uncompress.h vmalloc.h" omaps="mach-omap1 mach-omap2" mach_dir_old="arch/arm/plat-omap/include/mach" plat_dir_new="arch/arm/plat-omap/include/plat" mkdir -p $plat_dir_new git add $plat_dir_new for dir in $omaps; do mach_dir_new="arch/arm/$dir/include/mach" for header in $mach_files; do file="$mach_dir_new/$header" if [ ! -f $file ]; then echo -ne "/*\n * $file\n */\n\n#include <plat/$header>\n" > $file git add $file if [ ! -f $plat_dir_new/$header ]; then git mv $mach_dir_old/$header $plat_dir_new/$header fi fi done done Signed-off-by: Tony Lindgren <tony@atomide.com>
2009-10-20omap: headers: Move mtd-xip.h to be mach-omap1 specificTony Lindgren
These registers are omap1 specific. Signed-off-by: Tony Lindgren <tony@atomide.com>
2009-10-20omap: Split vmalloc.h for mach-omap1 and mach-omap2Tony Lindgren
Earlier patch "omap: Remap L3, L4 to get more kernel io address space" changed the VMALLOC_END. However, this change causes problems on mach-omap1: BUG: mapping for 0xe0000000 at 0xe0000000 overlaps vmalloc space BUG: mapping for 0xe1000000 at 0xe1000000 overlaps vmalloc space Fix this by creating separate vmalloc.h files for mach-omap1 and mach-omap2. Signed-off-by: Tony Lindgren <tony@atomide.com>
2009-10-20omap: headers: Split entry-macro.S for mach-omap1 and mach-omap2Tony Lindgren
Split entry-macro.S for mach-omap1 and mach-omap2 Signed-off-by: Tony Lindgren <tony@atomide.com>
2009-10-20omap: headers: Split debug-macro.S for mach-omap1 and mach-omap2Tony Lindgren
This also creates the include/mach subdirectories under mach-omap1 and mach-omap2. Signed-off-by: Tony Lindgren <tony@atomide.com>