Re: Choosing the correct framebuffer configuration
From: Geert Uytterhoeven <geert@linux-m68k.org>
Date: 2005-08-07 09:54:15
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
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
-------------------------------------------------------
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