summaryrefslogtreecommitdiff
path: root/src/mainboard/adlink
diff options
context:
space:
mode:
authorAngel Pons <th3fanbus@gmail.com>2021-06-14 09:39:01 +0200
committerPatrick Georgi <pgeorgi@google.com>2021-06-16 09:55:08 +0000
commit6a2a5142d5d18e44a4ec0268e51d594fa0e7a147 (patch)
tree04be835ad6bb957f73aefa33098225da77f2e756 /src/mainboard/adlink
parent3eeefba6a0b1be97b5de70ab9d485f8383472f15 (diff)
nb/intel/haswell: Fully handle GDXCBAR and EDRAMBAR
GDXCBAR and EDRAMBAR are accounted for when reporting resources to the allocator, but they are not present in the DSDT. In addition, coreboot does not enable either range, but MRC.bin sets up GDXCBAR and does not disable it afterwards. Not reporting GDXCBAR in the DSDT can result in resource conflicts, and not enabling EDRAMBAR can cause issues on CPUs with eDRAM. Enable both GDXCBAR and EDRAMBAR in coreboot code, and report these ranges in the DSDT. This matches what Broadwell does. The value for the `GDXC_BASE_ADDRESS` macro matches what MRC.bin programs as well. Tested on Asrock B85M Pro4 with an i7-4770S (no eDRAM): - Still boots - EDRAMBAR is now enabled with base address of 0xfed80000 - GDXCBAR is still mapped with base address of 0xfed84000 Change-Id: I5538873b30e3d02053e4ba125528d32453ef6572 Signed-off-by: Angel Pons <th3fanbus@gmail.com> Reviewed-on: https://review.coreboot.org/c/coreboot/+/55480 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Arthur Heymans <arthur@aheymans.xyz>
Diffstat (limited to 'src/mainboard/adlink')
0 files changed, 0 insertions, 0 deletions