Hi Geert,
ST-RAM (breaking the above assumption). Something similar is done for Amiga
chip RAM - exactly how does the chip RAM situation differ, Geert? Is chip
RAM being claimed by mem_init or is it being left aside?
Chip RAM is different in that Linux (unlike AmigaOS) doesn't use it as
system RAM.
Being on the Zorro II bus (first 16 MiB), it's slow on most machines and doesn't
support RMW cycles (needed for page tables) on Zorro III-capable machines.
In general, we don't use Z2 RAM as system memory on Z3 capable machines.
But is its physical address lower than the kernel segment's, as in this case?
(thanks to Andreas for the discontigmem commit pointer ... )
It's limited to 24-bit addresses.
Thanks, that's what I could not find on the spot.
Looks like we'll have to fix the bootstrap or our discontig memory
support. Is there a strict requirement (from the kernel's early
startup and mem_init POV) that the kernel has to reside in the first
bootinfo memory chunk?
Cheers,
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
