Linux Framebuffer Layer development
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Michel Dänzer" <michel@daenzer.net>
Cc: linux-fbdev-devel@lists.sourceforge.net,
	Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: Choosing the correct framebuffer configuration
Date: Sun, 07 Aug 2005 18:14:59 +0200	[thread overview]
Message-ID: <1123431300.30257.116.camel@gaston> (raw)
In-Reply-To: <1123430435.3848.332.camel@localhost>


> > The problem is that the radeonfb driver sees bpp = 32 and then sets
> > rgbt = 8/8/8/8. It stomps rgbt without looking at it.
> 
> Looks like a radeonfb bug.

It's not a bug :) radeonfb doesn't support anything but that format for
now. If you want to do something else, implement it :)
> 
> > The basic problem is what happens if bpp and rgbt are set in
> > conflicting ways. For example bpp = 16 and rgbt = 8/8/8/8. Which one
> > should win?
> 
> Read what you quoted from Geert above.
> 
> 



-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf

  reply	other threads:[~2005-08-07 16:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-06  1:47 Choosing the correct framebuffer configuration Jon Smirl
2005-08-06 23:12 ` Petr Vandrovec
2005-08-07  9:48 ` Geert Uytterhoeven
2005-08-07 15:33   ` Jon Smirl
2005-08-07 16:00     ` Michel Dänzer
2005-08-07 16:14       ` Benjamin Herrenschmidt [this message]
2005-08-07 16:32         ` Michel Dänzer
2005-08-07 16:53           ` Jon Smirl
2005-08-07 20:34             ` Geert Uytterhoeven
2005-08-07 20:38             ` Michel Dänzer
2005-08-07 20:47             ` Antonino A. Daplas
2005-08-07 16:15       ` Jon Smirl
2005-08-07 11:00 ` 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=1123431300.30257.116.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=michel@daenzer.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