Hi Petr, >> Certainly - 640x...@1bit isn't much. Even less than sthigh IIRC. > > sthigh is 640x...@1bit, I believe, i.e. even less than vga2. >
I stand corrected. >> I wonder why it does depend on FastRAM size, though. ST-RAM eaten up >> by page tables? > > why anything is stored in ST-RAM? Besides there's 14 MB of ST-RAM on > ARAnyM, that should be plenty (compare with Falcon's 4 MB). Due to some problem with memory management, the kernel treats all RAM as equal, and allocates from the bottom up apparently. The frame buffer is initialized rather late in the kernel init procedure, and both kernel, ramdisk image and ramdisk will go into ST-RAM. Maybe it's due to fragmentation of memory more than actual memory usage in the end. Ideally you would want to have the kernel, ramdisk etc. in FastRAM. This would require FastRAM to be placed as the first memory chunk in the bootinfo struct (for reasons of memory management setup that I've forgotten the details of - maybe it's time to revisit that ...). Anything I tried to remedy that has just failed to boot, so we seem stuck with kernel in ST-RAM. Cheers, Michael -- To unsubscribe from this list: send the line "unsubscribe linux-m68k" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
