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>
This commit is contained in:
@@ -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)
|
||||
|
Reference in New Issue
Block a user