From: Jon Smirl <jonsmirl@gmail.com>
To: linux-fbdev-devel@lists.sourceforge.net,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: DRI developer's list <dri-devel@lists.sourceforge.net>
Subject: Re: [Linux-fbdev-devel] CRTC scanout buffer types
Date: Sun, 7 Aug 2005 09:41:53 -0400 [thread overview]
Message-ID: <9e47339105080706414faf1e40@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0508071135450.31010@gorilla.sonytel.be>
I'm trying to work out a syntax for the sysfs attribute that will
control the config. My first idea is to use a alpha/red/blue/green
syntax. When red is set and blue/green are missing index mode is set.
When green is set and red/blue are missing gray scale is set.
Are there chips that can scanout from buffers not packed at a power of two?
How should I work different color spaces (YCbCr) into this?
4bpp Index = /4
4bpp greyscale = //4
8bpp Index = /8
8bpp RGB 332 = /3/3/2
8bpp greyscale = //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
24bpp aRGB 6666 = 6/6/6/6
32bpp aRGB 8888 = 8/8/8/8
32bpp aRGB 2:10:10:10 = 2/10/10/10
How are these packed?
1 bpp monochrome (black = 0 and white = 1 or vice versa)
1 bpp indexed
2 bpp indexed
3 bpp indexed
5 bpp indexed
6 bpp indexed
7 bpp indexed
These would have the same config, //8, right? You then just control
what you write to the byte.
8 bpp monochrome (black is all zeroes and white is all ones or vice versa)
8 bpp greyscale
How does this work, is one 24 bit color the key?
32 bpp indexed+RGB 888 with color key to enable RGB888
--
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 prev parent reply other threads:[~2005-08-07 13:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-05 20:19 CRTC scanout buffer types Jon Smirl
2005-08-06 23:23 ` Patrick McFarland
2005-08-06 23:27 ` Jon Smirl
2005-08-06 23:45 ` Dave Airlie
2005-08-07 9:43 ` Geert Uytterhoeven
2005-08-07 13:41 ` Jon Smirl [this message]
2005-08-07 20:42 ` Geert Uytterhoeven
2005-08-07 21:03 ` [Linux-fbdev-devel] " Ian Romanick
2005-08-07 21:45 ` Antonino A. Daplas
2005-08-07 22:31 ` [Linux-fbdev-devel] " Vladimir Dergachev
2005-08-08 1:15 ` Antonino A. Daplas
2005-08-08 2:05 ` [Linux-fbdev-devel] " Vladimir Dergachev
2005-08-08 2:33 ` Jon Smirl
2005-08-08 5:52 ` Antonino A. Daplas
2005-08-08 8:39 ` Geert Uytterhoeven
2005-08-08 13:14 ` [Linux-fbdev-devel] " Jon Smirl
2005-08-07 21:10 ` Antonino A. Daplas
2005-08-08 8:41 ` Geert Uytterhoeven
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=9e47339105080706414faf1e40@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=dri-devel@lists.sourceforge.net \
--cc=geert@linux-m68k.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.