From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 92220] GL_NV_vdpau_interop partially available Date: Fri, 02 Oct 2015 00:23:20 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0288177462==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id D1CD47A0EA for ; Thu, 1 Oct 2015 17:23:19 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0288177462== Content-Type: multipart/alternative; boundary="1443745399.8bB7fF631.25999"; charset="UTF-8" --1443745399.8bB7fF631.25999 Date: Fri, 2 Oct 2015 00:23:19 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" 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. --1443745399.8bB7fF631.25999 Date: Fri, 2 Oct 2015 00:23:19 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 4 on bug 92220 from 
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.
--1443745399.8bB7fF631.25999-- --===============0288177462== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0 cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWwK --===============0288177462==--