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 14:26:00 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0020888236==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 37C82721D5 for ; Fri, 2 Oct 2015 07:26:00 -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 --===============0020888236== Content-Type: multipart/alternative; boundary="1443795960.3BadF16C1.26380"; charset="UTF-8" --1443795960.3BadF16C1.26380 Date: Fri, 2 Oct 2015 14:26:00 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=92220 --- Comment #7 from Alex Deucher --- (In reply to riaasm from comment #4) > 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. It does require certain hardware features, namely decoding to separate fields. That's why we only enable it on UVD 2.2 and newer. Older UVD hardware only supports decoding to a full frame. > > 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? The hardware needs to support certain features to allow you to implement a software extension. E.g., consider tessellation. If your GPU does not support tessellation, it does not make sense to expose the GL extension since the implementation would be done in software which is slow. In the case of this extension, we could implement support for older UVD versions, but it involves an extra copies. > > 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. > We know which parts support decoding to fields. UVD 2.2 and newer. UVD 1.0-2.1 (R6xx, RS780, RS880, RV770, RV790) - don't support decoding to fields UVD 2.2 and newer (RV710, RV730, RV740, evergreen, NI, SI, CI, VI) - support decoding to fields > 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. We only expose the extension on asics that support it (UVD 2.2 and newer). Kodi already supports that by checking if the extension is enabled. The issue is what to do about older UVD versions that do not support the entire extension. All UVD versions support the part of the extension that kodi uses with it's current default settings. -- You are receiving this mail because: You are the assignee for the bug. --1443795960.3BadF16C1.26380 Date: Fri, 2 Oct 2015 14:26:00 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 7 on bug 92220 from 
(In reply to riaasm from comment #4)
> 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. 

It does require certain hardware features, namely decoding to separate fields. 
That's why we only enable it on UVD 2.2 and newer.  Older UVD hardware only
supports decoding to a full frame.

> 
> 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?

The hardware needs to support certain features to allow you to implement a
software extension.  E.g., consider tessellation.  If your GPU does not support
tessellation, it does not make sense to expose the GL extension since the
implementation would be done in software which is slow.  In the case of this
extension, we could implement support for older UVD versions, but it involves
an extra copies.

> 
> 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. 
> 

We know which parts support decoding to fields.  UVD 2.2 and newer.

UVD 1.0-2.1 (R6xx, RS780, RS880, RV770, RV790) - don't support decoding to
fields
UVD 2.2 and newer (RV710, RV730, RV740, evergreen, NI, SI, CI, VI) - support
decoding to fields

> 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.

We only expose the extension on asics that support it (UVD 2.2 and newer). 
Kodi already supports that by checking if the extension is enabled.  The issue
is what to do about older UVD versions that do not support the entire
extension.  All UVD versions support the part of the extension that kodi uses
with it's current default settings.

You are receiving this mail because:
  • You are the assignee for the bug.
--1443795960.3BadF16C1.26380-- --===============0020888236== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0 cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWwK --===============0020888236==--