Re: [PATCH v3 0/4] Atari kernel-in-FastRAM patches v3
>> Found the error, most likely - when the kernel runs in FastRAM,
>> m68k_num_memory is == 1. Is there a way to access the bootinfo view of the
>> number of memory chunks after the MMU init code has tweaked m68k_num_memory,
> You mean the ones that were removed due to "Ignoring memory chunk"?
These ones exactly.
> No, bootinfo is gone, unless saved for kexec with CONFIG_BOOTINFO_PROC=y.
> What exactly is the issue?
When deciding whether a ST-RAM DMA buffer needs to be allocated, the
Atari SCSI driver checks whether there's more than a single chunk of
RAM (there's always ST-RAM, so the second one indicates FastRAM).
That's no longer a good test now with the kernel capable of running
from FastRAM (and the ST-RAM chunk being dropped in MM init).
Maybe we need another variable to hold the number of memory chunks
before adjustment. Or look at size or physical base address of the
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- email@example.com
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds