diff options
author | Timothy Pearson <tpearson@raptorengineeringinc.com> | 2015-03-13 13:27:58 -0500 |
---|---|---|
committer | Kyösti Mälkki <kyosti.malkki@gmail.com> | 2015-03-19 08:28:43 +0100 |
commit | 86f4ca5b4b99a799b403e61a90aa24d103fb7f2f (patch) | |
tree | db0e317ff1a0bba502ba0fa7f748e9d8b8c99eb3 /src/mainboard/amd/parmer | |
parent | e24f7d37cef5acb71c070f934a74286efb6ee32e (diff) | |
download | coreboot-86f4ca5b4b99a799b403e61a90aa24d103fb7f2f.tar.xz |
cpu/amd/model_10xxx: Add support for early cbmem
mainboards/amd/fam10: Initialize cbmem area after raminit
When GFXUMA is enabled, CBMEM is placed at TOM - UMASIZE
When GFXUMA is disabled, CBMEM is placed at TOM
This matches the behaviour present before conversion to early
CBMEM.
The CBMEM location code implicitly assumes TOM does not change
between romstage and ramstage. TOM is set by romstage raminit,
and is never changed by romstage or ramstage afterward. As
the CBMEM location is positioned at a specific offset from TOM
that is known to both romstage and ramstage early CBMEM is safe
on Fam10h systems.
TEST: Booted ASUS KFSN4-DRE and verified both cbmem timestamp
tables from romstage and cbmem log tables from ramstage.
Change-Id: Idf9e0245fe91185696ff664b06182c26b376c196
Signed-off-by: Timothy Pearson <tpearson@raptorengineeringinc.com>
Reviewed-on: http://review.coreboot.org/8489
Tested-by: build bot (Jenkins)
Reviewed-by: Kyösti Mälkki <kyosti.malkki@gmail.com>
Tested-by: Raptor Engineering Automated Test Stand <noreply@raptorengineeringinc.com>
Diffstat (limited to 'src/mainboard/amd/parmer')
0 files changed, 0 insertions, 0 deletions