All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@gmail.com>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Opinions about YUV framebuffers
Date: Sun, 07 Aug 2005 17:52:27 +0800	[thread overview]
Message-ID: <42F5D9DB.1040007@gmail.com> (raw)
In-Reply-To: <ba2a6a4405080700015bfebaed@mail.gmail.com>

Nishant Kamat wrote:
> Hi experts,
> 
> I'd like to solicit some opinions about using the fbdev API for a
> display controller that accepts data in YUV format. fbcon seems to be
> written to work only for RGB framebuffers. Is that correct? Would it

No support for YUV formats but fbcon can be made to work with YUV formats.
For packed pixel, all you need to do is add another define in struct
fb_fix_screeninfo.visual (ie FB_VISUAL_YUV_PACKED, FB_VISUAL_YUV_PLANAR),
set info->pseudo_palette entries properly (in fb_setcolreg), do little
adjustments to cfb_* generic drawing functions so they recognize your new
visual formats and that's it.  

For planar formats, you need to write your own imageblit, copyarea and
fillrect.
  
> require lot of change to make it work with YUV data? Can X be run on
> YUV framebuffers?

I don't know if X supports YUV formats, and I also don't know how difficult
it will be to add support for it in X.   You can start with X's fbdev driver.

Tony


-------------------------------------------------------
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

  reply	other threads:[~2005-08-07  9:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-07  7:01 Opinions about YUV framebuffers Nishant Kamat
2005-08-07  9:52 ` Antonino A. Daplas [this message]
2005-08-07  9:58 ` 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=42F5D9DB.1040007@gmail.com \
    --to=adaplas@gmail.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.