Hi Michael,
Thank you - anyone testing these please note that the Falcon SCSI DMA
dribble buffer handling in the SCSI patch is still faulty. You should
_not_ attempt to use SCSI when running the kernel in FastRAM.
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,
Geert?
You mean the ones that were removed due to "Ignoring memory chunk"?
No, bootinfo is gone, unless saved for kexec with CONFIG_BOOTINFO_PROC=y.
What exactly is the issue?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx
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
--
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
