public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: lapinlam@vega.lnet.lut.fi (Tomi Lapinlampi),
	Adrian Bunk <bunk@stusta.de>
Cc: linux-kernel@vger.kernel.org, torvalds@osdl.org, rth@twiddle.net,
	adaplas@pol.net, linux-fbdev-devel@lists.sourceforge.net
Subject: Re: 2.6.12-rc3 compile failure in tgafb.c, tgafb not working anymore
Date: Mon, 25 Apr 2005 11:21:14 +0800	[thread overview]
Message-ID: <200504251121.16609.adaplas@hotpop.com> (raw)
In-Reply-To: <20050422144047.GY607@vega.lnet.lut.fi>

On Friday 22 April 2005 22:40, Tomi Lapinlampi wrote:
> On Fri, Apr 22, 2005 at 02:20:30PM +0300, Tomi Lapinlampi wrote:
> > Actually, I was able to get a clean compile with the patch from
> > http://marc.theaimsgroup.com/?l=linux-alpha&m=111392038121433&w=2
>
> Hi again,
>
> Although the tgafb driver compiles with the above patch, it shows
> similar behaviour as before: The kernel loads, the monitor comes alive
> but the screen stays completely blank.
> The last kernel that worked was 2.6.8.1. I've tested with 2.6.{9,10,11}

What does fbset show?  If the line rgba shows all zero, then you will get a
blank screen. The driver must properly set info->var.green|red|blue|transp,
which in turn depends on the hardware configuration.

You can try to insert these in tgafb_pci_register() after fb_find_mode().

If at 8bpp pseudocolor:

all->info.var.green.length = 8;
all->info.var.red.length = 8;
all->info.var.blue.length = 8;
all->info.var.green.offset = 0;
all->info.var.red.offset = 0;
all->info.var.blue.offset = 0;

If at 32-bit truecolor:

all->info.var.green.length = 8;
all->info.var.red.length = 8;
all->info.var.blue.length = 8;
all->info.var.green.offset = 8;
all->info.var.red.offset = 16;
all->info.var.blue.offset = 0;

If the above changes work, a definitive fix is still needed, one that will
also set the above for each visual the hardware supports on each
fb_check_var().

Tony



      parent reply	other threads:[~2005-04-25  3:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-21 18:50 2.6.12-rc3 compile failure in tgafb.c Tomi Lapinlampi
2005-04-21 20:43 ` Adrian Bunk
2005-04-22  7:28   ` Tomi Lapinlampi
2005-04-22 11:20     ` Tomi Lapinlampi
2005-04-22 14:40       ` 2.6.12-rc3 compile failure in tgafb.c, tgafb not working anymore Tomi Lapinlampi
2005-04-22 17:26         ` Linus Torvalds
2005-04-22 17:44           ` Maciej W. Rozycki
2005-04-22 17:51             ` Linus Torvalds
2005-04-22 18:07               ` Maciej W. Rozycki
2005-04-22 19:51               ` [Linux-fbdev-devel] " Geert Uytterhoeven
2005-04-25  3:21         ` Antonino A. Daplas [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=200504251121.16609.adaplas@hotpop.com \
    --to=adaplas@hotpop.com \
    --cc=adaplas@pol.net \
    --cc=bunk@stusta.de \
    --cc=lapinlam@vega.lnet.lut.fi \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rth@twiddle.net \
    --cc=torvalds@osdl.org \
    /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