]> git.karo-electronics.de Git - linux-beck.git/commit
ARM: move iotable mappings within the vmalloc region
authorNicolas Pitre <nicolas.pitre@linaro.org>
Thu, 25 Aug 2011 04:35:59 +0000 (00:35 -0400)
committerNicolas Pitre <nico@fluxnic.net>
Sun, 27 Nov 2011 00:21:26 +0000 (19:21 -0500)
commit0536bdf33faff4d940ac094c77998cfac368cfff
tree802e858f7c2771fa2e0939037a2ec3d3df742ff3
parentbe9b7335e70696bee731c152429b1737e42fe163
ARM: move iotable mappings within the vmalloc region

In order to remove the build time variation between different SOCs with
regards to VMALLOC_END, the iotable mappings are now allocated inside
the vmalloc region.  This allows for VMALLOC_END to be identical across
all machines.

The value for VMALLOC_END is now set to 0xff000000 which is right where
the consistent DMA area starts.

To accommodate all static mappings on machines with possible highmem usage,
the default vmalloc area size is changed to 240 MB so that VMALLOC_START
is no higher than 0xf0000000 by default.

Signed-off-by: Nicolas Pitre <nicolas.pitre@linaro.org>
Tested-by: Stephen Warren <swarren@nvidia.com>
Tested-by: Kevin Hilman <khilman@ti.com>
Tested-by: Jamie Iles <jamie@jamieiles.com>
Documentation/arm/memory.txt
arch/arm/include/asm/pgtable.h
arch/arm/mm/mmu.c