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: Sat, 03 Oct 2015 09:24:17 +0000	[thread overview]
Message-ID: <bug-92220-502-sO08sU7N4F@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-92220-502@http.bugs.freedesktop.org/>


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

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

--- Comment #10 from riaasm@yahoo.com ---
So if I understand this correctly, all versions of UVD can perform frame-based
interop. I assume that the UVD hardware was created to perform frame-based
interop, but after the GL_NV_vdpau_interop extension was
proposed/suggested/completed by Nvidia the UVD hardware was updated to also
allow field-based interop. The version in which this update was done is UVD
2.2. 

This explains why the UVD hardware only partially supports the GL extension,
since it wasn't aware of the extension at the time the UVD hardware was
created. Is this correct?

If so, userspace apps that only need frame-based interop can just check if UVD
is available since it should work on any UVD hardware. And userspace apps that
need field-based interop can check for the GL extension. Would this be a
reasonable and correct way to check for interop functionality

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

[-- Attachment #1.2: Type: text/html, Size: 1729 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-03  9:24 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
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 [this message]
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-sO08sU7N4F@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