linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: Thomas Winischhofer <thomas@winischhofer.net>,
	linux-fbdev-devel@lists.sourceforge.net
Subject: Re: 2.6.7 still garbage upon start
Date: Fri, 18 Jun 2004 09:45:06 +0800	[thread overview]
Message-ID: <200406180945.06335.adaplas@hotpop.com> (raw)
In-Reply-To: <40D21E31.5070904@winischhofer.net>

On Friday 18 June 2004 06:41, Thomas Winischhofer wrote:
> modprobing fbcon still paints a white rectangle. Difference to 2.6.6 is
> that this rectangle now fills the entire screen instead of a smaller
> area. As before, text is shown all correctly (painted upon the
> rectangle), and the white rectangle scrolls up just like text and in the
> end vanishes.
>

The white screen is the result of fbdev being initialized before vgacon is
deinitialized.  I can't find a simple solution for this except to disable vgacon
if fbcon is compiled statically.  Currently vgacon is always enabled in X86, so
I use this in drivers/video/console/Kconfig.

config VGA_CONSOLE
	bool "VGA text console" if EMBEDDED || !X86
	depends on !ARCH_ACORN && !ARCH_EBSA110 && !4xx && !8xx && !SPARC32 &&	!SPARC64 && !M68K && FRAMEBUFFER_CONSOLE != y

> Switching to another VT while in X still leaves you with a blank screen
> and a blinking cursor. If one presses return, the screen contents is
> restored.

You mean switching from X to another VT?  At least you just get a blank screen,
with other drivers, sometimes the machine hangs. 

(I have code I'm planning to send for RFC that will notify the low-level driver if 
switching from KD_GRAPHICS->KD_TEXT and vice versa or if multiple
drivers are mapped to different consoles. However, it seems BenH already has
code for this so I'm holding the submission.  I just can't find BenH's changes in
2.6.7 or -mm.  Hey Ben, where is it?)  

Tony




-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND

  reply	other threads:[~2004-06-18  1:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-17 22:41 2.6.7 still garbage upon start Thomas Winischhofer
2004-06-18  1:45 ` Antonino A. Daplas [this message]
2004-06-18  7:54   ` Thomas Winischhofer
2004-06-18  8:23     ` Geert Uytterhoeven
2004-06-18 13:08       ` John Zielinski
2004-06-18 13:18         ` Geert Uytterhoeven
2004-06-18 13:40           ` John Zielinski
2004-06-18 18:40           ` Antonino A. Daplas
2004-06-19  2:09             ` John Zielinski
2004-06-19  3:08             ` David Eger
2004-06-19  6:13               ` Antonino A. Daplas
2004-06-22  9:45                 ` David Eger
2004-06-22 13:20                   ` Antonino A. Daplas
2004-06-19 19:27             ` John Zielinski
2004-06-19 20:25               ` Antonino A. Daplas
2004-06-18 10:04     ` Antonino A. Daplas

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=200406180945.06335.adaplas@hotpop.com \
    --to=adaplas@hotpop.com \
    --cc=adaplas@pol.net \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=thomas@winischhofer.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).