From a6130fc8f9c00e0c545389b4e407f0b745435a56 Mon Sep 17 00:00:00 2001 From: Kyösti Mälkki Date: Mon, 12 May 2014 15:00:03 +0300 Subject: intel: Drop obsolete comments on MTRR usage MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Problem with UMA region allocation was fixed when MTRRs changed to use memrange implementation. Change-Id: I420dac30de2836a91596d81f88bb45b46f248532 Signed-off-by: Kyösti Mälkki Reviewed-on: http://review.coreboot.org/5719 Tested-by: build bot (Jenkins) Reviewed-by: Aaron Durbin Reviewed-by: Edward O'Callaghan --- src/include/device/device.h | 4 ---- 1 file changed, 4 deletions(-) (limited to 'src/include/device/device.h') diff --git a/src/include/device/device.h b/src/include/device/device.h index dfebeaa6f8..0ae4f888b3 100644 --- a/src/include/device/device.h +++ b/src/include/device/device.h @@ -211,10 +211,6 @@ void fixed_mem_resource(device_t dev, unsigned long index, /* It is the caller's responsibility to adjust regions such that ram_resource() * and mmio_resource() do not overlap. - * - * Current MTRR setup creates exclusive uncacheable holes for uma_resource() - * only and these are allowed to overlap any ram_resource(). This approach - * is used for all UMA except Intel Sandy/IvyBridge. */ #define ram_resource(dev, idx, basek, sizek) \ fixed_mem_resource(dev, idx, basek, sizek, IORESOURCE_CACHEABLE) -- cgit v1.2.3