[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: aranym vs atafb

On Thu, Dec 27, 2007 at 04:21:13AM +0100, Michael Schmitz wrote:

> > I've been trying to get d-i initrds to work with aranym without
> > trashing the screen [0]. I noticed something interesting in my testing
> > today.

> IIRC any addresses in that range (i.e. above 0xffffff) are aliased down to
> fit in 24 bit (ST-RAM on the Falcon only decodes 24 bit, and the VIDEL
> needs to use ST-RAM). Basically, you used up all available ST-RAM with the
> ramdisk and now force the framebuffer to use an invalid address (one which
> you can perfectly well write to, but the VIDEL cannot read from there).
> What you see on the screen is whatever is located at address 0x00700000
> and thereabouts (may be kernel memory, may be data/buffer cache).

That totally makes sense.

> The ramdisk load code needs to make sure a ramdisk is not loaded where it
> might interfere with other uses of ST-RAM (i.e. frame buffer or DMA bounce
> buffers for SCSI). Where does the ramdisk get loaded at, anyway? Is the
> kernel loaded in ST-RAM also?

How do I find out?

I put all the relevant parts including the boot log at 

> > I tried all the atafb configurations listed, but I couldn't get a
> > working result and have a ramdisk. The Floppy setting doesn't trash
> > the screen but we don't have any initrd's small enough.
> We need to load them somewhere else, FWIS. Meaning in TT-RAM.

Is that kernel hacking or a parameter?

> > I don't suppose we can build a bootable cdrom for atari?
> Uh, nope. CD-ROM drivers are a bad can of worms as it were, no idea what
> would even be supported by the CT60 (and it's all closed source). Unless
> you count booting from MiNT (assuming that can even be done).

Pretty much what I figured.



Stephen R. Marenka     If life's not fun, you're not doing it right!

Attachment: signature.asc
Description: Digital signature

Reply to: