summaryrefslogtreecommitdiffstats
path: root/drivers/rtc/rtc-sirfsoc.c
diff options
context:
space:
mode:
authorArd Biesheuvel <ard.biesheuvel@linaro.org>2016-03-30 15:18:42 +0200
committerWill Deacon <will.deacon@arm.com>2016-04-14 17:20:45 +0200
commit177e15f0c1444cd392374ec7175c4787fd911369 (patch)
tree9259c8fc1afb276bc606efb72aa34f5ac9b2ff72 /drivers/rtc/rtc-sirfsoc.c
parentRevert "arm64: account for sparsemem section alignment when choosing vmemmap ... (diff)
downloadlinux-177e15f0c1444cd392374ec7175c4787fd911369.tar.xz
linux-177e15f0c1444cd392374ec7175c4787fd911369.zip
arm64: add the initrd region to the linear mapping explicitly
Instead of going out of our way to relocate the initrd if it turns out to occupy memory that is not covered by the linear mapping, just add the initrd to the linear mapping. This puts the burden on the bootloader to pass initrd= and mem= options that are mutually consistent. Note that, since the placement of the linear region in the PA space is also dependent on the placement of the kernel Image, which may reside anywhere in memory, we may still end up with a situation where the initrd and the kernel Image are simply too far apart to be covered by the linear region. Since we now leave it up to the bootloader to pass the initrd in memory that is guaranteed to be accessible by the kernel, add a mention of this to the arm64 boot protocol specification as well. Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org> Signed-off-by: Will Deacon <will.deacon@arm.com>
Diffstat (limited to 'drivers/rtc/rtc-sirfsoc.c')
0 files changed, 0 insertions, 0 deletions