m68k: switch to MEMBLOCK + NO_BOOTMEM
In m68k the physical memory is described by [memory_start, memory_end] for !MMU variant and by m68k_memory array of memory ranges for the MMU version. This information is directly use to register the physical memory with memblock. The reserve_bootmem() calls are replaced with memblock_reserve() and the bootmap bitmap allocation is simply dropped. Since the MMU variant creates early mappings only for the small part of the memory we force bottom-up allocations in memblock. Signed-off-by: Mike Rapoport <rppt@linux.vnet.ibm.com> Acked-by: Greg Ungerer <gerg@linux-m68k.org> Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
This commit is contained in:

committed by
Geert Uytterhoeven

parent
9e09221957
commit
1008a11590
@@ -123,10 +123,6 @@ static void __init sun3_bootmem_alloc(unsigned long memory_start,
|
||||
availmem = memory_start;
|
||||
|
||||
m68k_setup_node(0);
|
||||
availmem += init_bootmem(start_page, num_pages);
|
||||
availmem = (availmem + (PAGE_SIZE-1)) & PAGE_MASK;
|
||||
|
||||
free_bootmem(__pa(availmem), memory_end - (availmem));
|
||||
}
|
||||
|
||||
|
||||
|
Reference in New Issue
Block a user