summaryrefslogtreecommitdiff
path: root/arch/arm/cpu
diff options
context:
space:
mode:
authorStephen Warren <swarren@nvidia.com>2012-09-20 09:29:03 +0000
committerTom Warren <twarren@nvidia.com>2012-10-29 09:07:04 -0700
commit7f1b767aea949d954e75fa635968a9d315d2e7ff (patch)
tree6c7710043057941f22bc39cadd20881a08b9d7a9 /arch/arm/cpu
parent6bbda88384948808dd4050624a6c27d6d63265a1 (diff)
downloadu-boot-imx-7f1b767aea949d954e75fa635968a9d315d2e7ff.zip
u-boot-imx-7f1b767aea949d954e75fa635968a9d315d2e7ff.tar.gz
u-boot-imx-7f1b767aea949d954e75fa635968a9d315d2e7ff.tar.bz2
ARM: tegra: define CONFIG_SYS_BOOTMAPSZ
This define indicates the size of the memory region where it is safe to place data passed to the Linux kernel (ATAGs, DTB, initrd). The value needs to be: a) Less than or equal to RAM size. b) Small enough that the area is not within the kernel's highmem region, since the kernel cannot access ATAGs/DTB/initrd from highmem. c) Large enough to hold the kernel+DTB+initrd. 256M seems large enough for (c) in most circumstances, and small enough to satisfy (a) and (b) across any possible Tegra board. Note that the user can override this value via environment variable "bootm_mapsize" if needed. The advantage of defining BOOTMAPSZ is that we no longer need to define variable fdt_high in the default environment. Previously, we defined this to prevent the DTB from being relocated to the very end of RAM, which on most Tegra systems is within highmem, and hence which would cause boot failures. A user can still define this variable themselves if they want the FDT to be either left in-place wherever loaded, or copied to some other specific location. Similarly, there should no longer be a strict requirement for the user to define initrd_high if using an initrd. Signed-off-by: Stephen Warren <swarren@nvidia.com> Signed-off-by: Tom Warren <twarren@nvidia.com>
Diffstat (limited to 'arch/arm/cpu')
0 files changed, 0 insertions, 0 deletions