3f7e5815f4
Split the iop3xx mach type into iop32x and iop33x -- split the config symbols, and move the code in the mach-iop3xx directory to the mach-iop32x and mach-iop33x directories. Signed-off-by: Lennert Buytenhek <buytenh@wantstofly.org> Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
17 lines
580 B
C
17 lines
580 B
C
/*
|
|
* linux/include/asm-arm/arch-iop33x/vmalloc.h
|
|
*/
|
|
|
|
/*
|
|
* Just any arbitrary offset to the start of the vmalloc VM area: the
|
|
* current 8MB value just means that there will be a 8MB "hole" after the
|
|
* physical memory until the kernel virtual memory starts. That means that
|
|
* any out-of-bounds memory accesses will hopefully be caught.
|
|
* The vmalloc() routines leaves a hole of 4kB between each vmalloced
|
|
* area for the same reason. ;)
|
|
*/
|
|
//#define VMALLOC_END (0xe8000000)
|
|
/* increase usable physical RAM to ~992M per RMK */
|
|
#define VMALLOC_END (0xfe000000)
|
|
|