linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ondrej Zajicek <santiago@crfreenet.org>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Best way to support mulitple planes?
Date: Sun, 16 Sep 2007 19:12:05 +0200	[thread overview]
Message-ID: <20070916171205.GA8459@localhost.localdomain> (raw)
In-Reply-To: <1189910310.5344.18.camel@daplas>


[-- Attachment #1.1: Type: text/plain, Size: 1593 bytes --]

On Sun, Sep 16, 2007 at 10:38:30AM +0800, Antonino A. Daplas wrote:
> 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.

I always perceived fb device as a representation of a sequencer/scanner -
probably because almost all ioctls on a fbdev device make sense for
sequencer (and associated CRT controller and DAC).

> We do not have the infrastructure yet to separate output devices from
> the framebuffer so multi-head/mergefb implementations will still be
> driver specific.

I think it can be done with (almost) present infrastructure - 
one fb device per sequencer (sharing all memory of a card). We can
do  most of multi-head/mergedfb configurations using appropriate vxyres/pan
setting. Perhaps one new ioctl to assign output ports to sequencers and
one new sysfs option for optional memory split (separate parts of memory
accessible through each fb device instead of all memory accessible through
both fb devices).

-- 
Elen sila lumenn' omentielvo

Ondrej 'SanTiago' Zajicek (email: santiago@crfreenet.org, jabber: santiago@njs.netlab.cz)
OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net)
"To err is human -- to blame it on a computer is even more so."

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

[-- Attachment #2: Type: text/plain, Size: 228 bytes --]

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

[-- Attachment #3: Type: text/plain, Size: 182 bytes --]

_______________________________________________
Linux-fbdev-devel mailing list
Linux-fbdev-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-fbdev-devel

  reply	other threads:[~2007-09-16 17:12 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 [this message]
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=20070916171205.GA8459@localhost.localdomain \
    --to=santiago@crfreenet.org \
    --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).