All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Smirl <jonsmirl@gmail.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: fbdev <linux-fbdev-devel@lists.sourceforge.net>,
	"Antonino A. Daplas" <adaplas@hotpop.com>,
	James Simmons <jsimmons@infradead.org>
Subject: Re: fixing fbdev for various framebuffer configs
Date: Fri, 29 Jul 2005 07:30:56 -0400	[thread overview]
Message-ID: <9e473391050729043010d54af7@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0507291317080.5335@numbat.sonytel.be>

On 7/29/05, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> On Fri, 29 Jul 2005, 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
> > 64   GL_RGBA16
> 
> All above (and many more) can be handled fine, cfr.
> fb_var_screeninfo.{red,green,blue,transp}.
> 
> > 48   GL_FLOAT_RGB16
> > 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?
> 
> Floating point pixel values could be handled by a new nonstd flag:

Why non-standard? All of the current higher end ATI/Nvidia cards support it.

> 
>     #define FB_NONSTD_FLOAT     2
>     fb_var_screeninfo.nonstd |= FB_NONSTD_FLOAT
> 
> > What is the effect of alpha bits on the scanout buffer, do they do anything?
> 
> They determine the transparency of the pixel w.r.t. to the underlying plane, if
> the hardware supports it.
> 
> 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
> 


-- 
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 11:31 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 [this message]
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=9e473391050729043010d54af7@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.