dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 00:23:20 +0000	[thread overview]
Message-ID: <bug-92220-502-YABlEU0sLb@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-92220-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1392 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=92220

--- Comment #4 from riaasm@yahoo.com ---
I understand that you can't enable a GL extension if there's no support for it
in the hardware, but I think this specific GL extension doesn't require
anything specific in the hardware. 

>From what I understand, the GL_NV_vdpau_interop extension needs to be supported
in the driver, not in the hardware. In this Phoronix article
(http://www.phoronix.com/scan.php?page=news_item&px=MTQ2NjY) it is mentioned
that NVIDIA implemented support for this in their binary driver (not their
hardware). So doesn't this mean that supporting this extension fully can be
done by improving/expanding the implementation in the driver?

As for the field and frame issue, I don't really know much about that. But I do
know that there's UVD2 and UVD2.2, which is often also indicated as UVD2. Is it
possible that the "Early versions of UVD" that "did not support field based
output" could be the UVD2 ones and the newer ones that work correctly are
UVD2.2? Because being able to make that distinction could make it easier to
figure out if this extension will likely work or not. 

I assume that Kodi will not work with the UVD2, but will work with UVD2.2. If
UVD2.2 guarantees that VDPAU can be used, then that might be a good solution
too.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2212 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

  parent reply	other threads:[~2015-10-02  0:23 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 [this message]
2015-10-02  5:50 ` bugzilla-daemon
2015-10-02  7:58 ` bugzilla-daemon
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-YABlEU0sLb@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