From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 79223] extra vsync when reading back pixels in xbmc
Date: Wed, 28 May 2014 05:46:33 +0000 [thread overview]
Message-ID: <bug-79223-502-N95hPgf2dl@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-79223-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 413 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=79223
--- Comment #4 from Pierre Ossman <pierre-bugzilla@ossman.eu> ---
Any appropriate tracing tools for this?
I'm also seeing something else waiting for vsync. With glReadPixels() out of
the picture, and glXSwapIntervalMESA(0), I'm still getting 60 fps and no
tearing. Possibly related?
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1183 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
next prev parent reply other threads:[~2014-05-28 5:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-25 19:10 [Bug 79223] New: extra vsync when reading back pixels in xbmc bugzilla-daemon
2014-05-25 19:10 ` [Bug 79223] " bugzilla-daemon
2014-05-25 20:20 ` bugzilla-daemon
2014-05-28 3:09 ` bugzilla-daemon
2014-05-28 5:46 ` bugzilla-daemon [this message]
2014-05-28 7:03 ` bugzilla-daemon
2014-05-30 13:15 ` bugzilla-daemon
2014-05-30 13:21 ` bugzilla-daemon
2014-05-30 13:35 ` bugzilla-daemon
2014-05-30 13:47 ` bugzilla-daemon
2014-05-30 20:04 ` bugzilla-daemon
2014-05-30 21:23 ` bugzilla-daemon
2014-06-01 18:21 ` bugzilla-daemon
2014-06-02 7:07 ` bugzilla-daemon
2014-06-02 15:48 ` bugzilla-daemon
2014-06-02 19:24 ` bugzilla-daemon
2014-06-02 19:26 ` bugzilla-daemon
2014-06-03 6:34 ` bugzilla-daemon
2014-06-03 15:07 ` bugzilla-daemon
2019-11-19 8:49 ` 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-79223-502-N95hPgf2dl@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