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:38:30 +0800 [thread overview]
Message-ID: <1189910310.5344.18.camel@daplas> (raw)
In-Reply-To: <46E9ABBB.4040008@freescale.com>
On Thu, 2007-09-13 at 16:29 -0500, Timur Tabi wrote:
> Ville Syrjälä wrote:
>
>
> Would it be correct to say that applications expect the separate devices
> (/dev/fb0, /dev/fb1, etc) to represent different monitors?
>
That's not necessarily true. In the strictest sense, each /dev/fbx
device represents one memory region. Whether that memory region is
attached to zero, one or more monitors is up to the driver.
We do not have the infrastructure yet to separate output devices from
the framebuffer so multi-head/mergefb implementations will still be
driver specific.
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/
_______________________________________________
Linux-fbdev-devel mailing list
Linux-fbdev-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-fbdev-devel
next prev parent reply other threads:[~2007-09-16 2:38 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 [this message]
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=1189910310.5344.18.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).