Linux Framebuffer Layer development
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@gmail.com>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: Choosing the correct framebuffer configuration
Date: Sun, 07 Aug 2005 19:00:55 +0800	[thread overview]
Message-ID: <42F5E9E7.6090809@gmail.com> (raw)
In-Reply-To: <9e473391050805184756f055ea@mail.gmail.com>

Jon Smirl wrote:
> If I understand things correctly the framebuffer config is supposed to
> be controlled by the transp/red/blue/green fields of fb_var_screeninfo
> during check_var. These fields are then combined to compute the
> bits_per_pixel.
> 
> radeonfb is working from the other direction, it starts with bpp and
> then computes ARGB. This looks wrong to me.
> 

> 16bpp aIndex 88 = 8/8

Set argb.length = 8, rgb.offset = 0, t.offset = 8.
The transp.offset differentiates ARGB8 from A8_RGB8.

Tony 


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

      parent reply	other threads:[~2005-08-07 11:00 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
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 [this message]

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=42F5E9E7.6090809@gmail.com \
    --to=adaplas@gmail.com \
    --cc=benh@kernel.crashing.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