Hi Geert,
Geert, Roman: does paging_init rely on part of the first memory chunk being
mapped in head.S, or just part of the chunk the kernel resides in? Could I
reorder the m68k_memory[] elements in setup.c to fix the ordering problems?
Should work. config_amiga() removes Zorro II memory chunks, and that's
just before
paging_init() is called. of course you cannot reorder the first chunk,
as that one is
already in use.
Found that out the hard way. So what's the fix for this? Does the first chunk
always have to be the one the kernel resides in?
What is the reason for dropping chunks that are residing below the fisrst one,
in paging_init ??
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
