All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 94470] VDPAU is broken  on TAHITI with MPV
Date: Wed, 09 Mar 2016 23:52:23 +0000	[thread overview]
Message-ID: <bug-94470-502@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 94470
           Summary: VDPAU is broken  on TAHITI with MPV
           Product: Mesa
           Version: git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: major
          Priority: medium
         Component: Drivers/Gallium/radeonsi
          Assignee: dri-devel@lists.freedesktop.org
          Reporter: jrch2k10@gmail.com
        QA Contact: dri-devel@lists.freedesktop.org

Hi guys, i just found out MPV is broken for VDPAU on my TAHITI card (AMD Radeon
R9-280), so i'm not sure when was it.

the error is as follow 
Mesa: User error: GL_INVALID_OPERATION in VDPAUMapSurfacesNV
[vo/opengl] after rendering: OpenGL error INVALID_OPERATION.
Mesa: User error: GL_INVALID_OPERATION in VDPAUMapSurfacesNV
[vo/opengl] after rendering: OpenGL error INVALID_OPERATION.
Mesa: User error: GL_INVALID_OPERATION in VDPAUMapSurfacesNV

[vo/opengl] after rendering: OpenGL error INVALID_OPERATION.
Mesa: User error: GL_INVALID_OPERATION in VDPAUMapSurfacesNV

[vo/opengl] after rendering: OpenGL error INVALID_OPERATION.
Mesa: User error: GL_INVALID_OPERATION in VDPAUMapSurfacesNV

[vo/opengl] after rendering: OpenGL error INVALID_OPERATION.
Mesa: User error: GL_INVALID_OPERATION in VDPAUMapSurfacesNV

[vo/opengl] after rendering: OpenGL error INVALID_OPERATION.
Mesa: User error: GL_INVALID_OPERATION in VDPAUMapSurfacesNV
AV: 00:00:02 / 00:20:45 (0%) A-V:  0.000


Exiting... (Quit)
[vo/opengl/vdpau-glx] Before uninitializing OpenGL interop: OpenGL error
INVALID_OPERATION.

MPV settings 
-vo=opengl[-hq] --hwdec=vdpau Filename

MPV works with 
-vo=vdpau --hwdec=vdpau Filename

Mesa/LLVM: today git 3dc2630e457155a4e8c8613911fe178bc4adf743
MPV: Today git d8b27ee4de4e26d594855960a4421b99db9e76ea

If you need more information please include instructions ;) not too saavy here
about Mesa debug and MESA_DEBUG=1 and LIBGL_DEBUG=verbose weren't of much help

TyVM for your hard work.

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

[-- Attachment #1.2: Type: text/html, Size: 3378 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2016-03-09 23:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-09 23:52 bugzilla-daemon [this message]
2016-03-10 14:04 ` [Bug 94470] VDPAU is broken on TAHITI with MPV bugzilla-daemon
2016-03-10 15:08 ` bugzilla-daemon
2016-03-10 15:12 ` bugzilla-daemon
2016-03-10 15:13 ` bugzilla-daemon
2016-03-10 15:18 ` bugzilla-daemon
2016-03-10 15:26 ` bugzilla-daemon
2016-03-10 15:49 ` bugzilla-daemon
2016-03-10 23:02 ` bugzilla-daemon
2016-03-30  2:25 ` bugzilla-daemon
2016-03-30  2:57 ` 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-94470-502@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.