02afa9a87b
For an XIP build, _etext does not represent the end of the binary image that needs to stay mapped into the MODULES_VADDR area. Years ago, data came before text in the memory map. However, now that the order is text/init/data, an XIP_KERNEL needs to map up to the data location in order to keep from cutting off parts of the kernel that are needed. We only map up to the beginning of data because data has already been copied, so there's no reason to keep it around anymore. A new symbol is created to make it clear what it is we are referring to. This fixes the bug where you might lose the end of your kernel area after page table setup is complete. Signed-off-by: Chris Brandt <chris.brandt@renesas.com> Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
9 lines
150 B
C
9 lines
150 B
C
#ifndef _ASM_ARM_SECTIONS_H
|
|
#define _ASM_ARM_SECTIONS_H
|
|
|
|
#include <asm-generic/sections.h>
|
|
|
|
extern char _exiprom[];
|
|
|
|
#endif /* _ASM_ARM_SECTIONS_H */
|