From: "Ville Syrjälä" <syrjala@sci.fi>
To: Keith Packard <keithp@keithp.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [RFC] drm: add overlays as first class KMS objects
Date: Tue, 26 Apr 2011 18:20:03 +0300 [thread overview]
Message-ID: <20110426152003.GA3093@sci.fi> (raw)
In-Reply-To: <yun39l5hqgt.fsf@aiko.keithp.com>
On Mon, Apr 25, 2011 at 04:16:18PM -0700, Keith Packard wrote:
> On Mon, 25 Apr 2011 15:12:20 -0700, Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
>
> > Overlays are a bit like half-CRTCs. They have a location and fb, but
> > don't drive outputs directly. Add support for handling them to the core
> > KMS code.
>
> Are overlays/underlays not associated with a specific CRTC? To my mind,
> overlays are another scanout buffer associated with a specific CRTC, so
> you'd create a scanout buffer and attach that to a specific scanout slot
> in a crtc, with the 'default' slot being the usual graphics plane.
And what if you don't have a "default" plane as such. For example, OMAP3
has one graphics plane and two video planes, and two output paths. Each
of the planes can be assigned to zero or one outputs. To accomodate this,
the design should allow for CRTCs without any scanout buffers.
Also a glance at DirectFB and OpenWF Display APIs might be helpful.
--
Ville Syrjälä
syrjala@sci.fi
http://www.sci.fi/~syrjala/
next prev parent reply other threads:[~2011-04-26 15:29 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-25 22:12 [RFC] drm: add overlays as first class KMS objects Jesse Barnes
2011-04-25 23:16 ` Keith Packard
2011-04-25 23:22 ` Jesse Barnes
2011-04-25 23:35 ` Stéphane Marchesin
2011-04-25 23:52 ` Jesse Barnes
2011-04-26 1:17 ` Keith Packard
2011-04-26 9:37 ` Alan Cox
2011-04-28 16:24 ` Rob Clark
2011-04-25 23:37 ` Keith Packard
2011-04-25 23:58 ` Jesse Barnes
2011-04-26 0:28 ` Alex Deucher
2011-04-26 0:33 ` Jesse Barnes
2011-04-26 14:01 ` Jerome Glisse
2011-04-26 14:16 ` Alan Cox
2011-04-26 15:11 ` Jerome Glisse
2011-04-26 15:29 ` Alan Cox
2011-04-26 10:01 ` Alan Cox
2011-04-26 15:16 ` Jesse Barnes
2011-04-28 16:32 ` Rob Clark
2011-04-26 15:20 ` Ville Syrjälä [this message]
2011-04-26 15:31 ` Jesse Barnes
2011-04-26 15:38 ` Alan Cox
2011-04-27 12:19 ` Daniel Vetter
2011-04-27 13:32 ` Jerome Glisse
2011-04-27 14:27 ` Daniel Vetter
2011-04-27 14:34 ` Chris Wilson
2011-04-27 14:50 ` Daniel Vetter
2011-04-27 14:56 ` Ville Syrjälä
2011-04-27 21:12 ` Jesse Barnes
2011-04-28 6:47 ` Daniel Vetter
2011-04-28 17:37 ` Jakob Bornecrantz
2011-04-28 17:03 ` Rob Clark
2011-04-28 17:54 ` Ville Syrjälä
2011-05-13 16:16 ` Daniel Vetter
2011-05-14 1:02 ` Jesse Barnes
2011-05-15 0:00 ` Clark, Rob
2011-05-17 18:35 ` Laurent Pinchart
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=20110426152003.GA3093@sci.fi \
--to=syrjala@sci.fi \
--cc=dri-devel@lists.freedesktop.org \
--cc=keithp@keithp.com \
/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.