From: "Michel Dänzer" <michel@daenzer.net>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: Choosing the correct framebuffer configuration
Date: Sun, 07 Aug 2005 12:00:35 -0400 [thread overview]
Message-ID: <1123430435.3848.332.camel@localhost> (raw)
In-Reply-To: <9e473391050807083327b190f9@mail.gmail.com>
On Sun, 2005-08-07 at 11:33 -0400, Jon Smirl wrote:
> On 8/7/05, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> > On Fri, 5 Aug 2005, Jon Smirl wrote:
> > > The chips actually allow nine configs (maybe more when I get a look at
> > > the R300 doc). It is ambiguous to set these configs based on BPP since
> > > there are multiple configs for various BPP. These configs should
> > > instead be set with the transp/red/blue/green fields.
> > >
> > > 4bpp Index = /4
> > > 8bpp Index = /8
> > > 16bpp aRGB 1555 = 1/5/5/5
> > > 16bpp RGB 565 = /5/6/5
> > > 16bpp aRGB 4444 = 4/4/4/4
> > > 16bpp aIndex 88 = 8/8
> > > 24bpp RGB 888 = /8/8/8
> > > 32bpp aRGB 8888 = 8/8/8/8
> > > 32bpp aRGB 2:10:10:10 = 2/10/10/10
> > >
> > > What is the best way to fix this?
> >
> > Just follow the FBIOPUT_VSCREENINFO rules:
> > - If a value doesn't fit, round it up.
> > - If rounding is impossible, return an error.
> >
> > So if a user asks for e.g. bpp 16, transp.length = 1,
> > {red,green,blue}.length = 0, you can give him 1555 if your hardware supports
> > it. Or 4444 if your hardware doesn't support anything in between 1000 and 4444
> > (w.r.t. rounding). But you must not give him 565, since this implies you
> > rounded down transp.length.
> >
> > > The interesting hidden config is 30b color.
> >
> > Piece of cake!
> >
> > bpp = 32
> > transp.length = 2, {red,green,blue}.length = 10
>
> 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.
> 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.
--
Earthling Michel Dänzer | Debian (powerpc), X and DRI developer
Libre software enthusiast | http://svcs.affero.net/rm.php?r=daenzer
-------------------------------------------------------
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
next prev parent reply other threads:[~2005-08-07 16:01 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 [this message]
2005-08-07 16:14 ` Benjamin Herrenschmidt
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=1123430435.3848.332.camel@localhost \
--to=michel@daenzer.net \
--cc=benh@kernel.crashing.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