From: Andreas Schwab <schwab@linux-m68k.org>
To: "Kolbjørn Barmen" <linux-m68k@kolla.no>
Cc: Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: Aranym, more than 244MB FastRAM, garbled display
Date: Fri, 01 Oct 2010 19:07:57 +0200 [thread overview]
Message-ID: <m2tyl5u9hu.fsf@igel.home> (raw)
In-Reply-To: <alpine.LNX.2.00.1010011728270.4788@halbrend.uninett.no> ("Kolbjørn Barmen"'s message of "Fri, 1 Oct 2010 17:49:33 +0200 (CEST)")
Kolbjørn Barmen <linux-m68k@kolla.no> writes:
> One thing I have noticed is that if I set FastRAM in aranym config to
> something higher than 244 I get garbled display, kinda like frozen random
> noise - the kernel does boot in the background though. I tried with
> different kernels (only up to 2.6.34 though), and with different versions
> of aranym, but it didn't make much difference.
I have always been using FastRAM = 256 without problems.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2010-10-01 17:08 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 [this message]
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 ` Aranym, more than 244MB FastRAM, garbled display Petr Stehlik
2010-10-11 8:11 ` 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=m2tyl5u9hu.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=linux-m68k@kolla.no \
--cc=linux-m68k@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox