Searched hist:"5 e98947f9baa5bdc9b819d365f9f8ef65a9b1e4d" (Results 1 – 2 of 2) sorted by relevance
| /rk3399_rockchip-uboot/arch/x86/cpu/coreboot/ |
| H A D | sdram.c | 5e98947f9baa5bdc9b819d365f9f8ef65a9b1e4d Thu Feb 28 19:26:10 UTC 2013 Simon Glass <sjg@chromium.org> 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>
|
| /rk3399_rockchip-uboot/arch/x86/lib/ |
| H A D | init_helpers.c | 5e98947f9baa5bdc9b819d365f9f8ef65a9b1e4d Thu Feb 28 19:26:10 UTC 2013 Simon Glass <sjg@chromium.org> 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>
|