summaryrefslogtreecommitdiffstats
path: root/scripts/config_whitelist.txt
diff options
context:
space:
mode:
authorAndre Przywara <andre.przywara@arm.com>2021-04-12 01:04:51 +0100
committerTom Rini <trini@konsulko.com>2021-04-20 07:31:12 -0400
commit109552d773e7aeb0f6417d8245fb0ecf01599ef3 (patch)
tree010a7fe67a4d74cd576341a854ff299d449c890a /scripts/config_whitelist.txt
parent84b2cd74f370dabb707e2611bf57714a66d08622 (diff)
downloadu-boot-109552d773e7aeb0f6417d8245fb0ecf01599ef3.tar.gz
u-boot-109552d773e7aeb0f6417d8245fb0ecf01599ef3.tar.xz
u-boot-109552d773e7aeb0f6417d8245fb0ecf01599ef3.zip
arm: highbank: Enable OF_CONTROL
All Calxeda machines are actually a poster book example of device tree usage: the DT is loaded from flash by the management processor into DRAM, the memory node is populated with the detected DRAM size and this DT is then handed over to the kernel. So it's a shame that U-Boot didn't participate in this chain, but fortunately this is easy to fix: Define CONFIG_OF_CONTROL and CONFIG_OF_BOARD, and provide a trivial function to tell U-Boot about the (fixed) location of the DTB in DRAM. Then enable DM_SERIAL, to let the PL011 driver pick up the UART platform data from the DT. Also define AHCI, to bring this driver into the driver model world as well. Signed-off-by: Andre Przywara <andre.przywara@arm.com>
Diffstat (limited to 'scripts/config_whitelist.txt')
0 files changed, 0 insertions, 0 deletions