diff options
| author | Kumar Gala <galak@kernel.crashing.org> | 2011-07-06 15:16:28 +0000 |
|---|---|---|
| committer | Wolfgang Denk <wd@denx.de> | 2011-07-26 13:55:10 +0200 |
| commit | 9e9579bbf9780ced1153371cdc6aeb1ea8f0c0b6 (patch) | |
| tree | 595b6695cbc96bdae6ac3a10670e4ad07ae7ae2b /post/board/pdm360ng | |
| parent | 3cfe6954893bd1790f0d6ad7f56fc95c0dc35232 (diff) | |
| download | u-boot-imx-9e9579bbf9780ced1153371cdc6aeb1ea8f0c0b6.zip u-boot-imx-9e9579bbf9780ced1153371cdc6aeb1ea8f0c0b6.tar.gz u-boot-imx-9e9579bbf9780ced1153371cdc6aeb1ea8f0c0b6.tar.bz2 | |
powerpc: Fix device tree padding associated with ramdisk
When booting with a ramdisk we bump the amount of memory reserved for
the device tree by FDT_RAMDISK_OVERHEAD. However we did not increase
the actual size in the device tree blob to match.
Its possible on boundary cases that we dont have enough memory according
to the device tree blob and get errors like:
WARNING: could not set linux,initrd-end FDT_ERR_NOSPACE
We can easily fix this by setting the device tree size at the same time
we bump the amount of memory reserved for the device tree.
Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
Acked-by: Gerald Van Baren <vanbaren@cideas.com>
Diffstat (limited to 'post/board/pdm360ng')
0 files changed, 0 insertions, 0 deletions