From: raof@ubuntu.com
To: dri-devel@lists.freedesktop.org
Cc: intel-gfx@lists.freedesktop.org,
Christopher James Halse Rogers <raof@ubuntu.com>,
Christopher James Halse Rogers
<christopher.halse.rogers@canonical.com>
Subject: [PATCH 2/2] drm/i915: support DRIVER_PRIME_SCANOUT.
Date: Tue, 4 Apr 2017 18:13:21 +1000 [thread overview]
Message-ID: <20170404081321.19263-3-raof@ubuntu.com> (raw)
In-Reply-To: <20170404081321.19263-1-raof@ubuntu.com>
From: Christopher James Halse Rogers <raof@ubuntu.com>
CC: intel-gfx@lists.freedesktop.org
Signed-off-by: Christopher James Halse Rogers <christopher.halse.rogers@canonical.com>
---
drivers/gpu/drm/i915/i915_drv.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/i915_drv.c b/drivers/gpu/drm/i915/i915_drv.c
index e703556eba99..0fbf8e4b7119 100644
--- a/drivers/gpu/drm/i915/i915_drv.c
+++ b/drivers/gpu/drm/i915/i915_drv.c
@@ -2575,7 +2575,7 @@ static struct drm_driver driver = {
*/
.driver_features =
DRIVER_HAVE_IRQ | DRIVER_IRQ_SHARED | DRIVER_GEM | DRIVER_PRIME |
- DRIVER_RENDER | DRIVER_MODESET,
+ DRIVER_RENDER | DRIVER_MODESET | DRIVER_PRIME_SCANOUT,
.open = i915_driver_open,
.lastclose = i915_driver_lastclose,
.preclose = i915_driver_preclose,
--
2.11.0
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2017-04-04 8:13 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-04 8:13 [PATCH] Tell userspace if scanning out of an imported PRIME buffer is safe raof
2017-04-04 8:13 ` [PATCH 1/2] drm: Add DRM_CAP_PRIME_SCANOUT raof
2017-04-04 8:31 ` Daniel Vetter
2017-04-04 10:11 ` Daniel Stone
2017-04-04 10:27 ` Christopher James Halse Rogers
2017-04-04 10:43 ` Lucas Stach
2017-04-04 11:53 ` Daniel Vetter
2017-04-05 0:20 ` Christopher James Halse Rogers
2017-04-05 6:27 ` Daniel Vetter
2017-04-05 6:52 ` Christopher James Halse Rogers
2017-04-05 8:15 ` Lucas Stach
2017-04-05 9:59 ` Daniel Vetter
2017-04-05 10:14 ` Lucas Stach
2017-04-05 11:13 ` Christopher James Halse Rogers
2017-04-05 11:21 ` Christian König
2017-04-10 8:52 ` Michel Dänzer
2017-04-10 9:03 ` Christian König
2017-04-10 14:10 ` Alex Deucher
2017-04-06 7:47 ` Christopher James Halse Rogers
2017-04-10 8:51 ` Michel Dänzer
2017-04-17 5:05 ` Christopher James Halse Rogers
2017-04-17 6:41 ` Michel Dänzer
2017-04-04 10:43 ` Daniel Stone
2017-04-04 11:15 ` Christian König
2017-04-04 11:32 ` Daniel Stone
2017-04-04 11:43 ` Christian König
2017-04-04 8:13 ` raof [this message]
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=20170404081321.19263-3-raof@ubuntu.com \
--to=raof@ubuntu.com \
--cc=christopher.halse.rogers@canonical.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 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.