All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 55913] Vdpau driver lag
Date: Mon, 22 Oct 2012 22:04:07 +0000	[thread overview]
Message-ID: <bug-55913-502-xbd3z8YRkj@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-55913-502@http.bugs.freedesktop.org/>


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

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

Grigori Goronzy <greg@chown.ath.cx> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|NOTOURBUG                   |---

--- Comment #4 from Grigori Goronzy <greg@chown.ath.cx> ---
mplayer2 uses advanced VDPAU functionality that mplayer does not use - the
presentation queue. This works fine with Nvidia's implementation. Likely the
bug is in Mesa's implementation of the presentation queue.

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

[-- Attachment #1.2: Type: text/html, Size: 2028 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:[~2012-10-22 22:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-12 11:56 [Bug 55913] New: Vdpau driver lag bugzilla-daemon
2012-10-12 11:57 ` [Bug 55913] " bugzilla-daemon
2012-10-12 12:09 ` bugzilla-daemon
2012-10-12 20:43 ` bugzilla-daemon
2012-10-12 23:53 ` bugzilla-daemon
2012-10-13 15:37 ` bugzilla-daemon
2012-10-22 22:04 ` bugzilla-daemon [this message]
2012-10-23 11:42 ` bugzilla-daemon
2019-09-18 19:01 ` 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-55913-502-xbd3z8YRkj@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.