linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@gmail.com>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Best way to support mulitple planes?
Date: Sun, 16 Sep 2007 10:45:09 +0800	[thread overview]
Message-ID: <1189910709.5344.23.camel@daplas> (raw)
In-Reply-To: <1189909973.5344.12.camel@daplas>

On Sun, 2007-09-16 at 10:32 +0800, Antonino A. Daplas wrote:
> On Thu, 2007-09-13 at 14:50 -0500, Timur Tabi wrote:
> > 
> > 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?
> 
> You can change the type from FB_TYPE_PLANES to FB_TYPE_PACKED_PIXELS in
> fb_fix_screeninfo.  That implies that for each SET_VAR ioctl, you do a
> GET_FIX ioctl.
> 

If you want separate /dev/fb's for each plane, then setup your own
notifier system so each of the /dev/fb's  can communicate with each
other.

See drivers/video/fb_notify.c, and look at
drivers/video/backlight/backlight.c, drivers/video/fbmem.c and
drivers/video/console/fbcon.c on how this communication is done.

Tony



-------------------------------------------------------------------------
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-16  2:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-13 19:50 Best way to support mulitple planes? Timur Tabi
2007-09-13 21:10 ` 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 [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=1189910709.5344.23.camel@daplas \
    --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 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).