From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jim Zhang <Zhang_Jim@cat.com>
Cc: intel-gfx@lists.freedesktop.org,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: colorkey support for intel i915 gpu driver
Date: Tue, 2 Apr 2019 15:31:34 +0300 [thread overview]
Message-ID: <20190402123134.GO3888@intel.com> (raw)
In-Reply-To: <SN6PR08MB4576227C3CF010DA8A69464388550@SN6PR08MB4576.namprd08.prod.outlook.com>
On Mon, Apr 01, 2019 at 08:18:13PM +0000, Jim Zhang wrote:
> Hi Sir/Madam:
>
> I am using the open source Baytrail gpu drm driver.
>
> Linux kernel version 3.10.61:
> Libdrm package: 2.4.97
>
> When calling function
> properties = drmModeObjectGetProperties(drmfd, plane_id, DRM_MODE_OBJECT_PLANE);
> it only returns only one property:
>
> This property is:
> property->name = "rotation", property->prop_id =4
> It looks like that the Baytrail gpu drm driver does not support colorkey.
There are two problems currently:
- Destination colorkey is not implemented on BYT/CHV. I have
patches for it but they have not been reviewed by anyone:
https://patchwork.freedesktop.org/series/43902/
- Colorkey can only be set via a custom i915 specific ioctl
(DRM_I915_SET_SPRITE_COLORKEY). There have been a few attempts at
a generic property based API that never really went anywhere. It's
a rather difficult problem making this generic as each hardware has
its own peculiar way of specifying colorkeying. The main problem
with the custom ioctl is that it's not atomic with other screen
updates.
So, what kind of use case do you have in mind?
--
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-04-02 12:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 20:18 colorkey support for intel i915 gpu driver Jim Zhang
2019-04-02 12:31 ` Ville Syrjälä [this message]
2019-04-09 13:29 ` Jim Zhang
2019-04-09 13:46 ` Ville Syrjälä
2019-04-09 13:56 ` Ville Syrjälä
2019-04-09 13:59 ` [Intel-gfx] " Jim Zhang
2019-04-09 14:17 ` Ville Syrjälä
2019-04-09 14:14 ` [Intel-gfx] " Jim Zhang
2019-04-09 14:19 ` Ville Syrjälä
2019-04-09 14:24 ` [Intel-gfx] " Jim Zhang
2019-04-09 15:01 ` Ville Syrjälä
2019-04-09 15:17 ` [Intel-gfx] " Jim Zhang
2019-04-09 19:15 ` Jim Zhang
2019-04-09 19:44 ` Ville Syrjälä
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=20190402123134.GO3888@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=Zhang_Jim@cat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.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;
as well as URLs for NNTP newsgroup(s).