linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jon Smirl <jonsmirl@gmail.com>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: "Antonino A. Daplas" <adaplas@hotpop.com>,
	James Simmons <jsimmons@infradead.org>
Subject: Re: fixing fbdev for various framebuffer configs
Date: Fri, 29 Jul 2005 08:13:17 -0400	[thread overview]
Message-ID: <9e47339105072905133da5fabc@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0507291356060.5335@numbat.sonytel.be>

On 7/29/05, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> On Fri, 29 Jul 2005, Jon Smirl wrote:
> > On 7/29/05, Antonino A. Daplas <adaplas@gmail.com> wrote:
> > > Jon Smirl wrote:
> > > > 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.
> > >
> > > To set for example, RGBA16, set {transp|green|red|blue}.len to 16, the
> > > offsets to 0, 16, 32, 48, and bits_per_pixel to 64.  Then let the driver
> > > sort it out.  I don't know what we can do about the FLOAT formats...
> > >
> > > >
> > > > Ideas on how to adjust the fbdev interface?
> > >
> > > Well, no need to adjust the interface.  But it is limited though to
> > > 16 bits per channel.  Redefining them to 32 will break a lot of apps.
> 
> It's only the colormap entries that are limited to 16 bits per color component,
> right? The color components in pixel values can be much larger (up to 2^31 bits
> :-).
> 
> > My current idea is to get rid of the bit_per_pixel attribute and
> > replace it with config. Config would take strings like 8,8,8 or
> > 5,5,5,1 or 32.,32.,32.
> 
> That's not acceptable. How do you differentiate between RGB888 (without alpha)
> using 24 or 32 bits per pixel?

Isn't that the driver's problem? You can't differentiate using OpenGL.
This does imply that I need a read only bits_per_pixel to allow apps
to caculate the stride.

> Or more general, what with hardware that has unused bits in its pixel values,
> e.g. hardware that has 8 bits per pixel but uses only 1 bit per byte in
> monochrome mode and 4 bits in 16-color mode?
> 
> > > > What is the effect of alpha bits on the scanout buffer, do they do anything?
> > >
> > > I think if there is another layer such as an overlay, the alpha bits can
> > > control the transparency between the framebuffer and the overlay. If only
> > > the framebuffer is active,  I don't believe it has any effects.
> 
> It has on e.g. Set Top Box hardware.
> 
> 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
> _______________________________________________
> Linux-fbdev-devel mailing list
> Linux-fbdev-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-fbdev-devel
> 


-- 
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

  reply	other threads:[~2005-07-29 12:13 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-29 10:53 fixing fbdev for various framebuffer configs Jon Smirl
2005-07-29 11:21 ` 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 [this message]
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=9e47339105072905133da5fabc@mail.gmail.com \
    --to=jonsmirl@gmail.com \
    --cc=adaplas@hotpop.com \
    --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).