From: Keith Packard <keithp@keithp.com>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [RFC] drm: add overlays as first class KMS objects
Date: Mon, 25 Apr 2011 16:37:46 -0700 [thread overview]
Message-ID: <yunzkndgawl.fsf@aiko.keithp.com> (raw)
In-Reply-To: <20110425162216.529c126c@jbarnes-desktop>
[-- Attachment #1.1: Type: text/plain, Size: 1062 bytes --]
On Mon, 25 Apr 2011 16:22:16 -0700, Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> Yes, that matches my understanding as well. I've deliberately made the
> implementation flexible there though, under the assumption that some
> hardware allows a plane to be directed at more than one CRTC (though
> probably not simultaneously).
So you create a scanout buffer and assign it to the appropriate slot in
the CRTC. Describing *how* the CRTC mixes pixels would be a good idea,
so the ordering of the slots might be relevant, and they might have a
blend mode (per-pixel alpha values, color key, separate alpha plane, etc).
> Arguably, this is something we should have done when the
> connector/encoder split was done (making planes in general first class
> objects). But with today's code, treating a CRTC as a pixel pump and a
> primary plane seems fine, with overlays tacked onto the side as
> secondary pixel sources but tied to a specific CRTC.
I know of hardware that needs a lot more than one overlay...
--
keith.packard@intel.com
[-- Attachment #1.2: Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2011-04-25 23:37 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 [this message]
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ä
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=yunzkndgawl.fsf@aiko.keithp.com \
--to=keithp@keithp.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.org \
/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