m68k: fix early memory reservation for ColdFire MMU systems
The bootmem to memblock conversion introduced by the commit 1008a11590
("m68k: switch to MEMBLOCK + NO_BOOTMEM") made reservation of kernel code
and data to start from a wrong address.
Fix it.
Signed-off-by: Mike Rapoport <rppt@linux.vnet.ibm.com>
Tested-by: Angelo Dureghello <angelo@sysam.it>
Signed-off-by: Greg Ungerer <gerg@linux-m68k.org>
This commit is contained in:
parent
57361846b5
commit
c90bbce9ee
|
@ -172,7 +172,7 @@ void __init cf_bootmem_alloc(void)
|
|||
high_memory = (void *)_ramend;
|
||||
|
||||
/* Reserve kernel text/data/bss */
|
||||
memblock_reserve(memstart, memstart - _rambase);
|
||||
memblock_reserve(_rambase, memstart - _rambase);
|
||||
|
||||
m68k_virt_to_node_shift = fls(_ramend - 1) - 6;
|
||||
module_fixup(NULL, __start_fixup, __stop_fixup);
|
||||
|
|
Loading…
Reference in New Issue