From: Jon Smirl <jonsmirl@gmail.com>
To: DRI developer's list <dri-devel@lists.sourceforge.net>,
fbdev <linux-fbdev-devel@lists.sourceforge.net>
Subject: CRTC scanout buffer types
Date: Fri, 5 Aug 2005 16:19:25 -0400 [thread overview]
Message-ID: <9e47339105080513195dee0804@mail.gmail.com> (raw)
I've included the scanout types for the R200, what other ones are
supported by the various chips? For example I think the R300 can
scanout in floating point.
4bpp Indexed
8bpp Indexed
16bpp aRGB 1555
16bpp RGB 565
24bpp RGB 888
32bpp aRGB 8888
16bpp aRGB 4444
16bpp aIndex 88
32bpp aRGB 2:10:10:10 palette bypassed
Note, the r200 supports a lot more buffer formats, but these are the
only ones valid for scanout.
--
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-08-05 20:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-05 20:19 Jon Smirl [this message]
2005-08-06 23:23 ` CRTC scanout buffer types 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 ` [Linux-fbdev-devel] " Jon Smirl
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=9e47339105080513195dee0804@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=dri-devel@lists.sourceforge.net \
--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.