linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Best way to support mulitple planes?
Date: Thu, 13 Sep 2007 14:50:54 -0500	[thread overview]
Message-ID: <46E9949E.30908@freescale.com> (raw)

Hi, I'm new to the framebuffer subsystem, so forgive me if this is a FAQ. 
I've spent the past couple hours scouring web sites and sample code, but I 
don't have a definitive answer to my question.

I have a device that supports three planes - memory areas that the hardware 
reads from to generate the physical image.  Each plane supports an alpha 
channel for each pixel, and the hardware just blends all three planes together 
when it draws the image.

Currently, our driver create three framebuffer devices, /dev/fb0, /dev/fb1, 
and /dev/fb2, which means three calls to register_framebuffer().  Is this the 
correct way to do it?

The reason I ask is that our hardware can only handle three planes if the 
resolution is 1024x768 or below.  I can't figure out any way of telling the 
framebuffer subsystem that if it switches to 1280x1024 in plane 0, that plane 
1 and 2 no longer exist.  Any suggestions on how to handle that?

-- 
Timur Tabi
Linux Kernel Developer @ Freescale

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

             reply	other threads:[~2007-09-13 19:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-13 19:50 Timur Tabi [this message]
2007-09-13 21:10 ` Best way to support mulitple planes? Ville Syrjälä
2007-09-13 21:29   ` Timur Tabi
2007-09-16  2:38     ` Antonino A. Daplas
2007-09-16 17:12       ` Ondrej Zajicek
2007-09-16  2:32 ` Antonino A. Daplas
2007-09-16  2:45   ` Antonino A. Daplas

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=46E9949E.30908@freescale.com \
    --to=timur@freescale.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).