From: Patrice Mandin <mandin.patrice@orange.fr>
To: linux-m68k@vger.kernel.org
Cc: debian-68k@lists.debian.org
Subject: Re: [PATCH 1/2] m68k/atari - stram: alloc ST-RAM pool even if kernel not in ST-RAM
Date: Thu, 20 Mar 2014 07:35:27 +0100 [thread overview]
Message-ID: <20140320073527.ab8b054090a48c09076e6068@orange.fr> (raw)
In-Reply-To: <1395213784-3249-1-git-send-email-schmitz@debian.org>
Hello,
I confirm there is a problem with stram/fastram usage. On my Falcon
+CT60, whenever I tried to run kernel from FastRam, nothing was
displayed on screen. The system was running because I could use it
through serial console, and see that everything was OK.
Of course, running the kernel from FastRam is much faster than running
it from STRam (something like 4x faster), so fixing this issue would be
very useful.
--
Patrice Mandin
WWW: http://pmandin.atari.org/
next prev parent reply other threads:[~2014-03-20 6:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 7:23 [PATCH 1/2] m68k/atari - stram: alloc ST-RAM pool even if kernel not in ST-RAM Michael Schmitz
2014-03-19 7:23 ` [PATCH 2/2] m68k/atari - atafb: convert allocation of fb ram to new interface Michael Schmitz
2014-03-19 8:01 ` Geert Uytterhoeven
2014-03-20 8:17 ` schmitz
2014-03-20 8:33 ` Geert Uytterhoeven
2014-03-22 1:28 ` schmitz
2014-03-22 7:36 ` schmitz
2014-03-19 7:51 ` [PATCH 1/2] m68k/atari - stram: alloc ST-RAM pool even if kernel not in ST-RAM Geert Uytterhoeven
2014-03-20 8:23 ` schmitz
2014-03-20 8:35 ` Geert Uytterhoeven
2014-03-22 1:32 ` schmitz
2014-03-23 20:02 ` Geert Uytterhoeven
2014-03-19 8:18 ` Andreas Schwab
2014-03-20 6:35 ` Patrice Mandin [this message]
2014-03-22 8:47 ` [PATCH 0/2] m68k/atari - make atafb work with kernel loaded to FastRAM Michael Schmitz
2014-03-23 0:28 ` schmitz
2014-03-22 8:47 ` [PATCH 1/2] m68k/atari - stram: alloc ST-RAM pool even if kernel not in ST-RAM Michael Schmitz
2014-03-22 8:47 ` [PATCH 2/2] m68k/atari - atafb: convert allocation of fb ram to new interface 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=20140320073527.ab8b054090a48c09076e6068@orange.fr \
--to=mandin.patrice@orange.fr \
--cc=debian-68k@lists.debian.org \
--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