diff options
author | Timur Tabi <timur@freescale.com> | 2010-05-24 15:10:25 -0500 |
---|---|---|
committer | Kumar Gala <galak@kernel.crashing.org> | 2010-10-20 02:28:00 -0500 |
commit | 43b08af53e12fd96bd818f9a5f8471a264496f07 (patch) | |
tree | a865517e13554a59d6c1552f0fa9a886388393a8 /arch/powerpc/cpu/mpc85xx/cpu.c | |
parent | a1964ea5c25238fdad254dbe88d1e4ed9cd84061 (diff) | |
download | u-boot-imx-43b08af53e12fd96bd818f9a5f8471a264496f07.zip u-boot-imx-43b08af53e12fd96bd818f9a5f8471a264496f07.tar.gz u-boot-imx-43b08af53e12fd96bd818f9a5f8471a264496f07.tar.bz2 |
always relocate fdt into an lmb-allocated memory block
The device tree (fdt) must always exist in within the bootmap (usually the
first 16MB of RAM). If it doesn't, then boot_relocate_fdt() will allocate
an LMB region in the bootmap and copy the fdt into that region. It will
also increase the size of the fdt.
If the fdt is already in the bootmap, then previously the memory was just
reserved. There was no contingency if the reservation failed, however.
By always allocating an lmb region and copying/resizing the fdt into that
region, the code is simplified and the memory region is always allocated
properly.
Also change the types of some variables to avoid some typecasts.
Signed-off-by: Timur Tabi <timur@freescale.com>
Tested-by: Ira Snyder <iws@ovro.caltech.edu>
Acked-by: Gerald Van Baren <vanbaren@cideas.com>
Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
Diffstat (limited to 'arch/powerpc/cpu/mpc85xx/cpu.c')
0 files changed, 0 insertions, 0 deletions