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>
Showing
- arch/m68k/Kconfig 3 additions, 0 deletionsarch/m68k/Kconfig
- arch/m68k/kernel/setup_mm.c 4 additions, 10 deletionsarch/m68k/kernel/setup_mm.c
- arch/m68k/kernel/setup_no.c 4 additions, 16 deletionsarch/m68k/kernel/setup_no.c
- arch/m68k/mm/init.c 0 additions, 1 deletionarch/m68k/mm/init.c
- arch/m68k/mm/mcfmmu.c 7 additions, 6 deletionsarch/m68k/mm/mcfmmu.c
- arch/m68k/mm/motorola.c 11 additions, 24 deletionsarch/m68k/mm/motorola.c
- arch/m68k/sun3/config.c 0 additions, 4 deletionsarch/m68k/sun3/config.c
Loading
Please register or sign in to comment