From: Bernie Thompson <bernie@plugable.com>
To: linux-fbdev@vger.kernel.org
Subject: fbdev: ARGB8888 vs. RGB888
Date: Sat, 02 Jan 2010 04:35:57 +0000 [thread overview]
Message-ID: <480988181001012035iccffebbn21ed0bb69d29a670@mail.gmail.com> (raw)
The udlfb (DisplayLink virtual USB) framebuffer driver currently
supports 16bpp (RGB565) only. Looking at adding 24/32bpp support.
Because it's a virtual device where the pixels get processed before
sending over USB, any pixel encoding on the host side could work.
Just have to choose the best one.
Anyone know of any surprising pros/cons which would lead one of
ARGB8888 or RGB888 being an obvious choice, all other things equal?
Is either mode known to work better for xf86-video-fbdev or other
client app compatibility?
RBG888 has several advantages, of course. One interesting advantage
of ARG8888 is udlfb has a mode where it's a defio client -- and larger
bpp means page faults are actually somewhat more precise in
identifying the damaged areas of the screen, in addition to natural
alignment advantages.
As background -- udlfb is in the kernel staging tree. And there is
some future work at git.plugable.com.
Thanks,
Bernie
http://plugable.com/
reply other threads:[~2010-01-02 4:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=480988181001012035iccffebbn21ed0bb69d29a670@mail.gmail.com \
--to=bernie@plugable.com \
--cc=linux-fbdev@vger.kernel.org \
/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).