From: Jon Smirl <jonsmirl@gmail.com>
To: fbdev <linux-fbdev-devel@lists.sourceforge.net>,
"Antonino A. Daplas" <adaplas@hotpop.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
James Simmons <jsimmons@infradead.org>
Subject: fixing fbdev for various framebuffer configs
Date: Fri, 29 Jul 2005 06:53:08 -0400 [thread overview]
Message-ID: <9e473391050729035370d76cc5@mail.gmail.com> (raw)
It has been determined that bits per pixel is insuffucient to
enumerate all the needed fbconfigs. Here are the possible fgconfigs
from the OpenGL headers:
total bits
8 GL_R3_G3_B2
8 GL_RGBA2
12 GL_RGB4
15 GL_RGB5
16 GL_R5_G6_B5
16 GL_RGBA4
16 GL_RGB5_A1
24 GL_RGB8
30 GL_RGB10
32 GL_RGBA8
32 GL_RGB10_A2
36 GL_RGB12
48 GL_RGB16
48 GL_RGBA12
48 GL_FLOAT_RGB16
64 GL_RGBA16
64 GL_FLOAT_RGBA16
96 GL_FLOAT_RGB32
128 GL_FLOAT_RGBA32
We need to be able to set any of these through the fbdev interface. We
also need to allow for possible future expansion.
Ideas on how to adjust the fbdev interface?
What is the effect of alpha bits on the scanout buffer, do they do anything?
--
Jon Smirl
jonsmirl@gmail.com
-------------------------------------------------------
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 reply other threads:[~2005-07-29 10:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-29 10:53 Jon Smirl [this message]
2005-07-29 11:21 ` fixing fbdev for various framebuffer configs Geert Uytterhoeven
2005-07-29 11:30 ` Jon Smirl
2005-07-29 12:25 ` Geert Uytterhoeven
2005-07-29 11:44 ` Antonino A. Daplas
2005-07-29 11:52 ` Jon Smirl
2005-07-29 12:01 ` Geert Uytterhoeven
2005-07-29 12:13 ` Jon Smirl
2005-07-29 12:17 ` Geert Uytterhoeven
2005-07-29 13:32 ` Antonino A. Daplas
2005-07-29 13:39 ` Jon Smirl
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=9e473391050729035370d76cc5@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=adaplas@hotpop.com \
--cc=geert@linux-m68k.org \
--cc=jsimmons@infradead.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).