From: Eric Blade <eblade@blackmagik.dynup.net>
To: James Simmons <jsimmons@infradead.org>
Cc: petero2@telia.com, linux-kernel@vger.kernel.org
Subject: Re: radeonfb patch for 2.4.22...
Date: Thu, 17 Jul 2003 18:43:31 -0400 [thread overview]
Message-ID: <3F172693.2060701@blackmagik.dynup.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0307171827260.10255-100000@phoenix.infradead.org>
James Simmons wrote:
>>This has been happening to me on my Radeon and on my Voodoo 3 for as
>>long as there has been framebuffers and they have in fact compiled and
>>worked. I thought this was normal?
>>
>>
>
>Its caused from switching from text mode to graphics mode. Take for
>example I have grabbed th epci regions for my voodoo card and then wrote
>to them. This was done before I switched to graphics mode. It messed up my
>vga text screen. So when we go from text to graphics we have stale data.
>
>
>
>
>
>
So, basically, it's normal, as I thought.
Perhaps a quick clear screen as it's initialized would be good...
--
----BEGIN GEEK CODE BLOCK----
Version: 3.1
GB/CS/MC/MU/O @d+ s:- a- C++++ UL++++ !P L+++ !E W+++ !N !o K? w--- @O++ !M !V PS+ PE- Y PGP- @t 5? X R tv-- b- DI++ D++ G e* h* r y+
----END GEEK CODE BLOCK----
next prev parent reply other threads:[~2003-07-17 23:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-16 10:59 radeonfb patch for 2.4.22 Eric Blade
2003-07-17 17:29 ` James Simmons
2003-07-17 22:43 ` Eric Blade [this message]
2003-07-18 17:42 ` James Simmons
[not found] <Pine.LNX.4.10.10307141237001.27519-100000@gate.crashing.org>
2003-07-14 18:11 ` Marcelo Tosatti
2003-07-14 18:30 ` ajoshi
2003-07-14 18:40 ` Marcelo Tosatti
2003-07-14 18:55 ` ajoshi
2003-07-14 19:11 ` Marcelo Tosatti
2003-07-14 19:34 ` Damian Kolkowski
2003-07-14 19:36 ` Marcelo Tosatti
2003-07-15 8:47 ` Benjamin Herrenschmidt
2003-07-15 7:44 ` Benjamin Herrenschmidt
2003-07-15 12:02 ` Peter Osterlund
2003-07-15 13:43 ` Benjamin Herrenschmidt
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=3F172693.2060701@blackmagik.dynup.net \
--to=eblade@blackmagik.dynup.net \
--cc=jsimmons@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=petero2@telia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).