Geert,
Does the hack below (not even compile-tested) work? It maps pool_size
(default 1 MiB) of ST-RAM and makes the pool use that.
Sort of - boots with kernel in ST-RAM, but nothing shown on the
screen. SCSI appears to allocate DMA-able memory though:
Turns out the test for kernel in ST-RAM is faulty. I'll have to find a
better test,
atafb_init: start
atafb_init: initializing Falcon hw
atafb: screen_base 007f4000 real_screen_base 007f4000 screen_len 69632
Determined 640x400, depth 1
virtual 640x870
Console: switching to mono frame buffer device 80x25
fb0: frame buffer device, using 68K of video memory
That's just the same behaviour as before, when the kernel was loaded to
FastRAM.
Cheers,
Michael
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
Archive: https://lists.debian.org/[email protected]
