aboutsummaryrefslogtreecommitdiff
path: root/src/include/device/device.h
diff options
context:
space:
mode:
authorKyösti Mälkki <kyosti.malkki@gmail.com>2014-05-12 15:00:03 +0300
committerKyösti Mälkki <kyosti.malkki@gmail.com>2014-05-14 07:30:20 +0200
commita6130fc8f9c00e0c545389b4e407f0b745435a56 (patch)
treee6256608d70f2765c046c706c821d3db80fe5bdb /src/include/device/device.h
parenta823f9b545b4a172c1c0f778b773f9ca13f0791e (diff)
intel: Drop obsolete comments on MTRR usage
Problem with UMA region allocation was fixed when MTRRs changed to use memrange implementation. Change-Id: I420dac30de2836a91596d81f88bb45b46f248532 Signed-off-by: Kyösti Mälkki <kyosti.malkki@gmail.com> Reviewed-on: http://review.coreboot.org/5719 Tested-by: build bot (Jenkins) Reviewed-by: Aaron Durbin <adurbin@google.com> Reviewed-by: Edward O'Callaghan <eocallaghan@alterapraxis.com>
Diffstat (limited to 'src/include/device/device.h')
-rw-r--r--src/include/device/device.h4
1 files changed, 0 insertions, 4 deletions
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)