linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Eger <eger@havoc.gtf.org>
To: adaplas@pol.net
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Jeff Garzik <garzik@havoc.gtf.org>,
	Linux Frame Buffer Device Development
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: 2.6.7 still garbage upon start
Date: Tue, 22 Jun 2004 05:45:01 -0400	[thread overview]
Message-ID: <20040622094501.GA29480@havoc.gtf.org> (raw)
In-Reply-To: <200406191413.03881.adaplas@hotpop.com>

On Sat, Jun 19, 2004 at 02:13:03PM +0800, Antonino A. Daplas wrote:
> On Saturday 19 June 2004 11:08, David Eger wrote:
> >
> > 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. 

You're absolutely correct.  

Unfortunately, removing the set_par() call from the PCI driver probe
code uncovered another problem.  For some reason, the VGA register writes
have to happen twice for the settings to take.  Jeff, this seems really
weird to me.  Do you have any idea why?  I sorta hate to leave in the hack:

cirrusfb_set_par_foo (info) {
	/* real register writes ... */
}

cirrusfb_set_par (info) {
	cirrusfb_set_par_foo (info);
	return cirrusfb_set_par_foo (info);
}

-dte


-------------------------------------------------------
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

  reply	other threads:[~2004-06-22  9:45 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
2004-06-22  9:45                 ` David Eger [this message]
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=20040622094501.GA29480@havoc.gtf.org \
    --to=eger@havoc.gtf.org \
    --cc=adaplas@pol.net \
    --cc=garzik@havoc.gtf.org \
    --cc=geert@linux-m68k.org \
    --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).