From: Geert Uytterhoeven <geert@linux-m68k.org>
To: "Rhee, C. Joon" <jrhee@qualcomm.com>
Cc: Linux Frame Buffer Device Development
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: YUV Framebuffer
Date: Wed, 17 Oct 2007 08:57:32 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0710170852350.29643@anakin> (raw)
In-Reply-To: <27AAC353AE72C840926448157F375E72012B59B1@NAEX17.na.qualcomm.com>
On Tue, 16 Oct 2007, Rhee, C. Joon wrote:
> Is it possible to create framebuffer color format in YUV (eg. YUV422
> interleaved) and expose it through /dev/fb?
>
> What would be fb_info type?
What do you mean with `interleaved'?
Even and odd frames are separate (interlace)?
For YUV422, you have to add a new visual type.
A long time ago, I used this for a non-public test project:
#define FB_TYPE_PACKED_PIXELS_LACED 5 /* Interlaced Packed Pixels */
#define FB_TYPE_PACKED_PIXELS_4AREAS 6 /* 4 areas of Packed Pixels */
#define FB_VISUAL_YCBCR422 6 /* YCbCr 4:2:2 */
#define FB_VISUAL_YCBCR420 7 /* YCbCr 4:2:0 */
> And how about about fb_var_screeninfo.green/blue/red offset?
Just assume red, green, and blue mean Y, U, and V?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next prev parent reply other threads:[~2007-10-17 6:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-17 0:00 YUV Framebuffer Rhee, C. Joon
2007-10-17 6:57 ` Geert Uytterhoeven [this message]
2007-10-17 17:07 ` Rhee, C. Joon
2007-10-17 19:45 ` Geert Uytterhoeven
2007-10-18 13:20 ` Antonino A. Daplas
2007-10-18 13:41 ` Geert Uytterhoeven
2007-10-18 23:03 ` Antonino A. Daplas
2007-10-19 7:13 ` 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=Pine.LNX.4.64.0710170852350.29643@anakin \
--to=geert@linux-m68k.org \
--cc=jrhee@qualcomm.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 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).