diff options
| author | Simon Glass <sjg@chromium.org> | 2013-02-28 19:26:10 +0000 |
|---|---|---|
| committer | Simon Glass <sjg@chromium.org> | 2013-03-04 15:56:46 -0800 |
| commit | 5e98947f9baa5bdc9b819d365f9f8ef65a9b1e4d (patch) | |
| tree | 3837fd16321542d20d654442752b419d84514709 /snapshot.commit | |
| parent | 2536850d7cd90bdb75bf3ff86838f913392b68db (diff) | |
| download | u-boot-imx-5e98947f9baa5bdc9b819d365f9f8ef65a9b1e4d.zip u-boot-imx-5e98947f9baa5bdc9b819d365f9f8ef65a9b1e4d.tar.gz u-boot-imx-5e98947f9baa5bdc9b819d365f9f8ef65a9b1e4d.tar.bz2 | |
x86: Add function to get top of usable ram
The memory layout calculations are done in calculate_relocation_address(),
and coreboot has its own version of this function. But in fact all we
really need is to set the top of usable RAM, and then the base version
will work as is.
So instead of allowing the whole calculate_relocation_address() function
to be replaced, create board_get_usable_ram_top() which can be used by
a board to specify the top of the area where U-Boot relocations to.
Signed-off-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'snapshot.commit')
0 files changed, 0 insertions, 0 deletions