diff options
| author | Kumar Gala <galak@kernel.crashing.org> | 2011-12-07 04:42:58 +0000 |
|---|---|---|
| committer | Wolfgang Denk <wd@denx.de> | 2011-12-12 08:17:52 +0100 |
| commit | 3b2001105fe4d0326f7aa1f83534accfdaec6a01 (patch) | |
| tree | 070b0f5a1c50a063d4bcd2629891ae57ab92ee1b /board/egnite | |
| parent | 02ab0970b3ae7b2d535a1231ad259e3114d09772 (diff) | |
| download | u-boot-imx-3b2001105fe4d0326f7aa1f83534accfdaec6a01.zip u-boot-imx-3b2001105fe4d0326f7aa1f83534accfdaec6a01.tar.gz u-boot-imx-3b2001105fe4d0326f7aa1f83534accfdaec6a01.tar.bz2 | |
powerpc/bootm: Flush ramdisk and device tree image when booting on MP
We already flush the kernel image after we've loaded it to ensure
visiblity to the other cores. We need to do the same thing for the
ramdisk and device tree images. In AMP boot scenarios we might not be
HW cache coherent with the secondary core that we are loading and
setting the ramdisk and device tree up for. Thus we need to ensure
we've flushed the regions of memory utilized by ramdisk and device tree
so the loadding and any modifications (from decompression or fdt updates)
are made visible to the secondary cores.
Signed-off-by: Kumar Gala <galak@kernel.crashing.org>
Diffstat (limited to 'board/egnite')
0 files changed, 0 insertions, 0 deletions