AMD and GFXUMA : drop redundant use of lb_add_memory_range()
See commit 505414a6cf
.
Change-Id: Icc04af9726ae54141581aecc84c40e8aac54591d
Signed-off-by: Kyösti Mälkki <kyosti.malkki@gmail.com>
Reviewed-on: http://review.coreboot.org/1378
Tested-by: build bot (Jenkins)
Reviewed-by: Anton Kochkov <anton.kochkov@gmail.com>
This commit is contained in:
parent
5e29f00c55
commit
9edd8e46f5
|
@ -51,16 +51,6 @@ static void parmer_enable(device_t dev)
|
|||
|
||||
int add_mainboard_resources(struct lb_memory *mem)
|
||||
{
|
||||
/* UMA is removed from system memory in the northbridge code, but
|
||||
* in some circumstances we want the memory mentioned as reserved.
|
||||
*/
|
||||
/* TODO: Check out why it was commented. */
|
||||
#if CONFIG_GFXUMA
|
||||
printk(BIOS_INFO, "uma_memory_start=0x%llx, uma_memory_size=0x%llx \n",
|
||||
uma_memory_base, uma_memory_size);
|
||||
lb_add_memory_range(mem, LB_MEM_RESERVED, uma_memory_base,
|
||||
uma_memory_size);
|
||||
#endif
|
||||
return 0;
|
||||
}
|
||||
struct chip_operations mainboard_ops = {
|
||||
|
|
Loading…
Reference in New Issue