Patrick Rudolph has uploaded this change for review. ( https://review.coreboot.org/c/coreboot/+/30609
Change subject: [WIP]cbmem_top: Fix comment and remove upper limit ......................................................................
[WIP]cbmem_top: Fix comment and remove upper limit
There's no such limit on 64bit coreboot builds. * Fix comment * Remove 4 GiB limit on Cavium SoCs
Change-Id: I8c9c6a5ff81bee48311e8bf8e383d1a032ea3a6d Signed-off-by: Patrick Rudolph patrick.rudolph@9elements.com --- M src/include/cbmem.h M src/soc/cavium/cn81xx/cbmem.c 2 files changed, 3 insertions(+), 3 deletions(-)
git pull ssh://review.coreboot.org:29418/coreboot refs/changes/09/30609/1
diff --git a/src/include/cbmem.h b/src/include/cbmem.h index ad48e35..66a8fbe 100644 --- a/src/include/cbmem.h +++ b/src/include/cbmem.h @@ -71,7 +71,8 @@
/* Return the top address for dynamic cbmem. The address returned needs to * be consistent across romstage and ramstage, and it is required to be - * below 4GiB. + * below 4GiB for 32bit coreboot builds. On 64bit coreboot builds there's no + * upper limit. * x86 boards or chipsets must return NULL before the cbmem backing store has * been initialized. */ void *cbmem_top(void); diff --git a/src/soc/cavium/cn81xx/cbmem.c b/src/soc/cavium/cn81xx/cbmem.c index 397fd26..9a52de3 100644 --- a/src/soc/cavium/cn81xx/cbmem.c +++ b/src/soc/cavium/cn81xx/cbmem.c @@ -22,6 +22,5 @@ void *cbmem_top(void) { /* Make sure not to overlap with reserved ATF scratchpad */ - return (void *)min((uintptr_t)_dram + (sdram_size_mb() - 1) * MiB, - 4ULL * GiB); + return (void *)((uintptr_t)_dram + (sdram_size_mb() - 1) * MiB); }