From: "Antonino A. Daplas" <adaplas@gmail.com>
To: linux-fbdev-devel@lists.sourceforge.net
Cc: Dennis Munsie <dmunsie@cecropia.com>
Subject: Re: YUV support
Date: Sat, 22 Jul 2006 05:19:45 +0800 [thread overview]
Message-ID: <44C144F1.4060608@gmail.com> (raw)
In-Reply-To: <A52F3235-4BC6-4B97-921D-5FFD642AA044@cecropia.com>
Dennis Munsie wrote:
> Hi again,
>
> I'm starting to investigate adding YUV support to the intelfb driver,
> and I was wondering what support is already in the framebuffer
> subsystem for YUV. Doing a quick grep for YUV only yielded a handful
> of references -- all in drivers. Nothing seems to be there for
> generic YUV support.
>
> Am I correct in this assumption?
Yes, you are correct.
> And, if so, what would be the best
> way to expose YUV support?
Create a new visual, FB_VISUAL_YUV_PACKED, then treat
var->{red,green,blue} as Y, U and V instead. This way, one can continue
to use the cfb_* generic drawing funtions.
For planar formats, it's pretty much the same except you have to provide
your own drawing functions.
> Driver specific ioctl's?
sysfs is probably better.
> Separate fb
> device for the YUV overlay?
Yes. Some drivers have fb0 for the primary, fb1 for the overlay, and fb2 for
the cursor.
> Give up and use X?
Or you can use directfb, I bet the i830 there has overlay support.
Tony
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
prev parent reply other threads:[~2006-07-21 21:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-21 21:08 YUV support Dennis Munsie
2006-07-21 21:19 ` 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=44C144F1.4060608@gmail.com \
--to=adaplas@gmail.com \
--cc=dmunsie@cecropia.com \
--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.