[coreboot-gerrit] New patch to review for coreboot: 36be5aa rambi: don't mark graphics as write-combining

[Aaron Durbin (adurbin@google.com)]

Aaron Durbin (adurbin at google.com) just uploaded a new patch set to gerrit, which you can find at http://review.coreboot.org/4908

-gerrit

commit 36be5aa25b57ce3dc59984eeb4173873e91584ee
Author: Aaron Durbin <adurbin at chromium.org>
Date:   Tue Oct 29 10:43:53 2013 -0500

    rambi: don't mark graphics as write-combining
    
    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 at chromium.org>
    Reviewed-on: https://chromium-review.googlesource.com/174653
    Reviewed-by: Duncan Laurie <dlaurie at chromium.org>
---
 src/mainboard/google/rambi/Kconfig | 1 -
 1 file changed, 1 deletion(-)

diff --git a/src/mainboard/google/rambi/Kconfig b/src/mainboard/google/rambi/Kconfig
index 1e2cc33..4c3b43b 100644
--- a/src/mainboard/google/rambi/Kconfig
+++ b/src/mainboard/google/rambi/Kconfig
@@ -14,7 +14,6 @@ config BOARD_SPECIFIC_OPTIONS
 	select HAVE_ACPI_RESUME
 	select MAINBOARD_HAS_CHROMEOS
 	select CHROMEOS
-	select MARK_GRAPHICS_MEM_WRCOMB
 
 config VBOOT_RAMSTAGE_INDEX
 	hex