Fix MB calculation in the reporting of the MTRR hole
Change-Id: I34b5c4ffd2a3f3e895d2bffedce1c00ee9aea942 Signed-off-by: Duncan Laurie <dlaurie@google.com> Reviewed-on: http://review.coreboot.org/763 Tested-by: build bot (Jenkins) Reviewed-by: Ronald G. Minnich <rminnich@gmail.com>
This commit is contained in:
parent
7389fa945f
commit
527fc74a83
|
@ -306,7 +306,7 @@ static unsigned int range_to_mtrr(unsigned int reg,
|
||||||
|
|
||||||
if (hole_sizek) {
|
if (hole_sizek) {
|
||||||
printk(BIOS_DEBUG, "Adding hole at %ldMB-%ldMB\n",
|
printk(BIOS_DEBUG, "Adding hole at %ldMB-%ldMB\n",
|
||||||
hole_startk, hole_startk + hole_sizek);
|
hole_startk >> 10, (hole_startk + hole_sizek) >> 10);
|
||||||
reg = range_to_mtrr(reg, hole_startk, hole_sizek,
|
reg = range_to_mtrr(reg, hole_startk, hole_sizek,
|
||||||
next_range_startk, MTRR_TYPE_UNCACHEABLE,
|
next_range_startk, MTRR_TYPE_UNCACHEABLE,
|
||||||
address_bits, above4gb);
|
address_bits, above4gb);
|
||||||
|
|
Loading…
Reference in New Issue