From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: John Zielinski <grim@undead.cc>
Cc: Linux Frame Buffer Device Development
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: radeonfb_pci_register video memory clear?
Date: Wed, 23 Jun 2004 10:52:57 -0500 [thread overview]
Message-ID: <1088005977.1854.140.camel@gaston> (raw)
In-Reply-To: <40D3A2E1.2060100@undead.cc>
On Fri, 2004-06-18 at 21:20, John Zielinski wrote:
> I'm just wondering why the clearing of video memory was added to
> radeonfb_pci_register? The memory still belongs to vgacon at this
> point. There are a few other problems with this: there is a noticable
> delay while the screen is totaly blank, vgacon can't save the text
> screen to the shadow buffer, and all further output until the takeover
> is invisible (vga font is wiped) so an oops here wouldn't be readable.
I added that to fix reports of users complaining they had garbage displayed
on boot. I didn't think about the interaction with vgacon (see, I have
absolutely no legacy hardware doing crappy VGA mode ;)
Maybe that should be reversed ....
Ben.
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
prev parent reply other threads:[~2004-06-23 16:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-19 2:20 radeonfb_pci_register video memory clear? John Zielinski
2004-06-19 19:27 ` Kronos
2004-06-19 19:46 ` John Zielinski
2004-06-23 15:56 ` Benjamin Herrenschmidt
2004-06-23 16:07 ` Geert Uytterhoeven
2004-06-23 15:52 ` Benjamin Herrenschmidt [this message]
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=1088005977.1854.140.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=grim@undead.cc \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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).