diff options
author | Alexander Graf <agraf@suse.de> | 2016-03-04 01:10:04 +0100 |
---|---|---|
committer | Tom Rini <trini@konsulko.com> | 2016-03-15 21:30:10 -0400 |
commit | 5d00995c361c5a01b0684927d2686fdb540ab467 (patch) | |
tree | 3522c68b25ae145c7148a22f3f8f3f86e8a2aae4 /board/bf525-ucr2/bf525-ucr2.c | |
parent | b9939336d09ddc01e9e9d4e6a654f54f28decb12 (diff) | |
download | u-boot-imx-5d00995c361c5a01b0684927d2686fdb540ab467.zip u-boot-imx-5d00995c361c5a01b0684927d2686fdb540ab467.tar.gz u-boot-imx-5d00995c361c5a01b0684927d2686fdb540ab467.tar.bz2 |
efi_loader: Implement memory allocation and map
The EFI loader needs to maintain views of memory - general system memory
windows as well as used locations inside those and potential runtime service
MMIO windows.
To manage all of these, add a few helpers that maintain an internal
representation of the map the similar to how the EFI API later on reports
it to the application.
For allocations, the scheme is very simple. We basically allow allocations
to replace chunks of previously done maps, so that a new LOADER_DATA
allocation for example can remove a piece of the RAM map. When no specific
address is given, we just take the highest possible address in the lowest
RAM map that fits the allocation size.
Signed-off-by: Alexander Graf <agraf@suse.de>
Tested-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'board/bf525-ucr2/bf525-ucr2.c')
0 files changed, 0 insertions, 0 deletions