From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 92220] GL_NV_vdpau_interop partially available
Date: Fri, 02 Oct 2015 07:58:29 +0000 [thread overview]
Message-ID: <bug-92220-502-QnlT3Tlom2@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-92220-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1043 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=92220
--- Comment #6 from riaasm@yahoo.com ---
Option 1 is a good workaround, but it needs to be done manually. Option 2 is of
course the easiest for userspace programs since they would not have to change
anything, but it might not be practical. I think for Kodi it would be preferred
to have a way to programmatically find out if this partial interop
functionality is available. This would be a fourth option.
For example, if someone can confirm that the interop functionality is not
available in UVD1 and UVD2, but partial interop is available in UVD2.2 and full
interop is available in UVD3 and higer, then perhaps the solution for programs
like Kodi would be to check the extension as well as the UVD version. Or if
someone can find out if there's some other way to distinguish between hardware
without interop support and with partial interop support (since both of these
will have the interop extension disabled).
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1762 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:[~2015-10-02 7:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 19:46 [Bug 92220] GL_NV_vdpau_interop partially implemented bugzilla-daemon
2015-10-01 19:59 ` bugzilla-daemon
2015-10-01 20:08 ` [Bug 92220] GL_NV_vdpau_interop partially available bugzilla-daemon
2015-10-01 20:19 ` bugzilla-daemon
2015-10-01 20:32 ` bugzilla-daemon
2015-10-02 0:23 ` bugzilla-daemon
2015-10-02 5:50 ` bugzilla-daemon
2015-10-02 7:58 ` bugzilla-daemon [this message]
2015-10-02 14:26 ` bugzilla-daemon
2015-10-02 14:27 ` bugzilla-daemon
2015-10-02 14:29 ` bugzilla-daemon
2015-10-03 9:24 ` bugzilla-daemon
2015-10-05 9:31 ` bugzilla-daemon
2015-10-05 11:50 ` bugzilla-daemon
2015-10-05 12:03 ` bugzilla-daemon
2015-10-05 13:31 ` bugzilla-daemon
2019-09-18 19:19 ` bugzilla-daemon
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=bug-92220-502-QnlT3Tlom2@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@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