Hi Geert,
What is the reason for dropping chunks that are residing below the fisrst one, in paging_init ??`git blame' tells you that code was added by commit 12d810c1b8c2b913d48e629e2b5c01d105029839 Author: Roman Zippel <zippel@xxxxxxxxxxxxxx> Date: Thu May 31 00:40:54 2007 -0700 m68k: discontinuous memory support Probably discontigmem supports only increasing physical addresses of the multiple memory chunks :-(
Looks like it... We can fix the bootstrap, but I fear that won't change a thing (I could not see where the early startup code would refer to the memory chunks at all).
But the newer sparsemem generic model may support it, see Documentation/memory-hotplug.txt.
Thanks, I'll have a look at that. Michael -- To unsubscribe from this list: send the line "unsubscribe linux-m68k" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
