From: Thorsten Glaser <tg@mirbsd.de>
Cc: linux-m68k@vger.kernel.org
Subject: Re: Atari console corruption
Date: Mon, 31 Jan 2011 22:04:21 +0000 (UTC) [thread overview]
Message-ID: <Pine.BSM.4.64L.1101312159540.30566@herc.mirbsd.org> (raw)
In-Reply-To: <AANLkTimEeLfHJrcFhk+38og1GDP1KZLaiXVqYRhMfhbc@mail.gmail.com>
Geert Uytterhoeven dixit:
>What does `fbset -i' say?
*installs fbset* (if it helps, the lightwhite text of linux_logo -uy
is fine, but the normal shell lightgrey on black looks yellowish)
mode "640x480-60"
# D: 25.176 MHz, H: 31.470 kHz, V: 59.943 Hz
geometry 640 480 640 960 4
timings 39720 42 18 31 11 100 3
rgba 4/0,4/0,4/0,0/0
endmode
Frame buffer device informaion:
Name : Atari Builtin
Address : 0xb27000
Size : 307200
Type : INTERLEAVED PLANES (2 bytes interleave)
Visual : PSEUDOCOLOR
XPanStep : 1
YPanStep : 1
YWrapStep : 0
LineLength : 320
Accelerator : Atari Blitter
Hm, so it appears I *am* using an interleaved mode but do not
have the corruption. Nice… (but then, this is an old kernel with
only a few of the modern patches… OTOH, I never saw it…)
ARAnyM config looks like:
[VIDEO]
FullScreen = No
BootColorDepth = 8
VidelRefresh = 1
and
Args = root=/dev/hda1 console=tty debug=par
(using video=atafb:vga2 is no longer needed thanks to the stram fix)
bye,
//mirabilos
--
22:20⎜<asarch> The crazy that persists in his craziness becomes a master
22:21⎜<asarch> And the distance between the craziness and geniality is
only measured by the success 22:21⎜<mksh> it’s a
very thin line anyway… with some, you don’t know which side they’re on
next prev parent reply other threads:[~2011-01-31 22:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-13 19:10 Atari console corruption Geert Uytterhoeven
2010-10-13 21:00 ` Andreas Schwab
2011-01-30 14:17 ` Thorsten Glaser
2011-01-30 18:55 ` Geert Uytterhoeven
2011-01-30 19:15 ` Thorsten Glaser
2011-01-31 18:32 ` Geert Uytterhoeven
2011-01-31 22:04 ` Thorsten Glaser [this message]
2011-01-31 1:46 ` Michael Schmitz
2022-07-11 11:37 ` Geert Uytterhoeven
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=Pine.BSM.4.64L.1101312159540.30566@herc.mirbsd.org \
--to=tg@mirbsd.de \
--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 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.