linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: David Eger <eger@havoc.gtf.org>, adaplas@pol.net
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	John Zielinski <grim@undead.cc>,
	Thomas Winischhofer <thomas@winischhofer.net>,
	Linux Frame Buffer Device Development
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: 2.6.7 still garbage upon start
Date: Sat, 19 Jun 2004 14:13:03 +0800	[thread overview]
Message-ID: <200406191413.03881.adaplas@hotpop.com> (raw)
In-Reply-To: <20040619030854.GB14319@havoc.gtf.org>

On Saturday 19 June 2004 11:08, David Eger wrote:
> On Sat, Jun 19, 2004 at 02:40:31AM +0800, Antonino A. Daplas wrote:
> > Actually, to eliminate the white rectangle, we just need to initialize
> > fbdev _after_ vgacon.  Currently, there is a set_par call in
> > fbcon_startup()) which is called prior to vgacon_deinit.
> >
> >  [snip]
> >
> > I've include a patch that incorporates all of the above.  (It also has
> > some fixes for problems with creation of logo space -- the code does not
> > consider that the new VC window size is different or even smaller than
> > the old VC window size). Please test, and if it works for you, I'll push
> > it upstream.
>
> with my cirrusfb driver and your patch, the area to the right of the
> penguins is cleared, but the area where the text is drawn still has
> white rectangle crud that scrolls off the screen.

Most probably, you are initializing your graphics card  before you register 
the framebuffer.  You should not do it, but only on an explict fb_set_par() 
call. If that cannot be avoided, we can extend the rectangle for fillrect() 
in fb_show_logo() - fbmem.c.  So instead of rect.height = 
fb_logo.logo->height, use info->var.xres (or info->var.yres_virtual). You 
might lose some of the text messages though, not sure.

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-19  6:13 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
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 [this message]
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=200406191413.03881.adaplas@hotpop.com \
    --to=adaplas@hotpop.com \
    --cc=adaplas@pol.net \
    --cc=eger@havoc.gtf.org \
    --cc=geert@linux-m68k.org \
    --cc=grim@undead.cc \
    --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).