vexpress64: fix various memory issues
authorLinus Walleij <linus.walleij@linaro.org>
Mon, 11 May 2015 08:03:57 +0000 (10:03 +0200)
committerTom Rini <trini@konsulko.com>
Wed, 27 May 2015 17:35:55 +0000 (13:35 -0400)
commit303557089f3db253eaec6f38dece204fd154b6ac
tree6944b538c12cfbd6f020c31f549b09fa73c8ee7b
parente186851ae4f0a4c8b75108930b61a5f74baf6ed4
vexpress64: fix various memory issues

The ARM Trusted Firmware or other security solutions are
eating memory from the top of the physical SDRAM1 space,
moving backward from 0xffffffff, currently occupying e.g.
0xfe000000-0xffffffff with Trusted Firmware.

This solution to reserving memory for secure world is not
optimal, so we need to think of how the secure world and
earlier boot stages should communicate to U-Boot what
memory they are eating up. For now let's just put 16MB
aside.

Also enable the memory test command and define start and
end of the test range so we can check that we actually have
all that memory available and working.

Suggested-by: Axel Haslam <ahaslam@baylibre.com>
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
include/configs/vexpress_aemv8a.h