mirror of
https://github.com/AsahiLinux/u-boot
synced 2024-11-12 16:07:30 +00:00
3b2001105f
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> |
||
|---|---|---|
| .. | ||
| _ashldi3.S | ||
| _ashrdi3.S | ||
| _lshrdi3.S | ||
| bat_rw.c | ||
| board.c | ||
| bootcount.c | ||
| bootm.c | ||
| cache.c | ||
| extable.c | ||
| interrupts.c | ||
| kgdb.c | ||
| Makefile | ||
| memcpy_mpc5200.c | ||
| ppccache.S | ||
| ppcstring.S | ||
| reloc.S | ||
| ticks.S | ||
| time.c | ||