From: Petr Stehlik <pstehlik@sophics.cz>
To: Michael Schmitz <schmitzmic@googlemail.com>
Cc: linux-m68k@vger.kernel.org
Subject: Re: Aranym, more than 244MB FastRAM, garbled display
Date: Thu, 07 Oct 2010 15:11:22 +0200 [thread overview]
Message-ID: <1286457082.1687.52.camel@joy-desktop> (raw)
In-Reply-To: <AANLkTi=ZrDoFPxFNZ3OKurvcrBuN3fS0gTvAeYpLQqCi@mail.gmail.com>
Michael Schmitz píše v Thu 07. 10. 2010 v 09:47 +0200:
> >>> Args = root=/dev/hda1 console=tty debug=par video=atafb:vga2
> >
> >>The problem starts happening as soon as FastRAM >= 512.
> >
> > I suspect atafb:vga2 reduces the amount of memory needed enough
> > for it to work.
>
> Certainly - 640x480@1bit isn't much. Even less than sthigh IIRC.
sthigh is 640x400@1bit, I believe, i.e. even less than vga2.
> 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).
Petr
next prev parent reply other threads:[~2010-10-07 16:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-01 15:49 Aranym, more than 244MB FastRAM, garbled display Kolbjørn Barmen
2010-10-01 17:07 ` Andreas Schwab
2010-10-01 17:09 ` Kolbjørn Barmen
2010-10-04 19:49 ` Thorsten Glaser
2010-10-05 6:47 ` Geert Uytterhoeven
2010-10-06 9:22 ` Thorsten Glaser
2010-10-07 7:47 ` Michael Schmitz
2010-10-07 8:22 ` Geert Uytterhoeven
2010-10-11 8:00 ` Michael Schmitz
2010-10-22 7:42 ` [PATCH] m68k atari: reserve some ST-RAM early on for device buffer use (was: Re: Aranym, more than 244MB FastRAM, garbled display) Michael Schmitz
2010-10-22 9:05 ` Andreas Schwab
2010-10-24 4:11 ` Michael Schmitz
2010-12-05 11:11 ` Geert Uytterhoeven
2010-10-07 13:11 ` Petr Stehlik [this message]
2010-10-11 8:11 ` Aranym, more than 244MB FastRAM, garbled display Michael Schmitz
2010-10-01 17:17 ` Geert Uytterhoeven
2010-10-04 7:51 ` Michael Schmitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1286457082.1687.52.camel@joy-desktop \
--to=pstehlik@sophics.cz \
--cc=linux-m68k@vger.kernel.org \
--cc=schmitzmic@googlemail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.