From: Daniel Vetter <daniel@ffwll.ch>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: Plane support for SNB and IVB
Date: Mon, 12 Dec 2011 22:21:43 +0100 [thread overview]
Message-ID: <20111212212113.GB5773@phenom.ffwll.local> (raw)
In-Reply-To: <1323289763-1963-1-git-send-email-jbarnes@virtuousgeek.org>
On Wed, Dec 07, 2011 at 12:29:20PM -0800, Jesse Barnes wrote:
> I think the core support is ready now, but I'd like feedback on the
> color key ioctl. It would be good to have a way to disable it at
> runtime (w/o color keying enabled, the sprite will always sit on top of
> the primary), and potentially add alpha support at some point.
>
> Would 0 as the color key work well enough as a "disable" flag? Or
> should I add a separate field to the ioctl? Anyone have a preference?
0 is black and I can image a legit color key with "black bars". Any other
value makes the interface kinda ad-hoc. So a separate field preferred.
-Daniel
--
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48
next prev parent reply other threads:[~2011-12-12 21:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-07 20:29 Plane support for SNB and IVB Jesse Barnes
2011-12-07 20:29 ` [PATCH 1/3] drm/i915: add SNB and IVB video sprite support v5 Jesse Barnes
2011-12-12 21:56 ` Daniel Vetter
2011-12-13 19:46 ` Jesse Barnes
2011-12-13 21:11 ` Jesse Barnes
2011-12-07 20:29 ` [PATCH 2/3] drm/i915: add destination color key support Jesse Barnes
2011-12-12 22:14 ` Daniel Vetter
2011-12-07 20:29 ` [PATCH 3/3] drm/i915: track sprite coverage and disable primary plane if possible Jesse Barnes
2011-12-12 22:17 ` Daniel Vetter
2011-12-08 2:58 ` Plane support for SNB and IVB Hai Lan
2011-12-12 21:21 ` Daniel Vetter [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-12-19 11:23 Konstantin Belousov
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=20111212212113.GB5773@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@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