erebion/coreboot
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

rambi: don't mark graphics as write-combining

Browse source 
We are currently running out of MTRRs with this CPU when
marking the graphics memory as write-combining. The reason
is that the graphics stolen memory was bumped to 64MiB which
changes the address space enough that the MTRRs are exhausted.

BUG=None
BRANCH=None
TEST=Built and analyzed MTRR usage. Also noted clearing upper
     2GiB of memory in depthcharge does not take forever.

Change-Id: I2eb0168990a5c585605f958e1cbc9ec1a2322d1d
Signed-off-by: Aaron Durbin <adurbin@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/174653
Reviewed-by: Duncan Laurie <dlaurie@chromium.org>
This commit is contained in:
Aaron Durbin 2013-10-29 10:43:53 -05:00 • committed by chrome-internal-fetch
commit b489622a1f
2 changed files with 0 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

1
configs/config.rambi
View file

@ -20,7 +20,6 @@ CONFIG_VGA_BIOS=y
CONFIG_VGA_BIOS_FILE="3rdparty/mainboard/google/rambi/vgabios.bin"
CONFIG_CPU_ADDR_BITS=36
CONFIG_CACHE_ROM=y
CONFIG_MARK_GRAPHICS_MEM_WRCOMB=y
CONFIG_ELOG=y
CONFIG_ELOG_GSMI=y
CONFIG_ELOG_BOOT_COUNT=y

1
src/mainboard/google/rambi/Kconfig
View file

@ -13,7 +13,6 @@ config BOARD_SPECIFIC_OPTIONS
select HAVE_OPTION_TABLE
select HAVE_ACPI_RESUME
select CHROMEOS
select MARK_GRAPHICS_MEM_WRCOMB
config VBOOT_RAMSTAGE_INDEX
hex