From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 98964] Chromium complains about glXGetSyncValuesOML in 13.0.2
Date: Sat, 03 Dec 2016 05:47:09 +0000 [thread overview]
Message-ID: <bug-98964-502-uBLK4Wsv2Z@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-98964-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 516 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=98964
--- Comment #6 from Zoltán Böszörményi <zboszor@pr.hu> ---
I don't know if it's a regression or if it's in Mesa at all.
When did Chromium started to use the vertical sync?
49 and 51 didn't print this, but it's true that we used 12.0.x or 11.1.x for
them.
On other machines with Intel J1900 CPU (i965) or AMD Kabini (radeonsi) this
message is not printed by Chromium.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1311 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
next prev parent reply other threads:[~2016-12-03 5:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 9:31 [Bug 98964] Chromium complains about glXGetSyncValuesOML in 13.0.2 bugzilla-daemon
2016-12-02 9:32 ` bugzilla-daemon
2016-12-02 19:40 ` bugzilla-daemon
2016-12-03 5:47 ` bugzilla-daemon [this message]
2016-12-05 21:58 ` bugzilla-daemon
2016-12-05 22:00 ` bugzilla-daemon
2016-12-06 5:18 ` bugzilla-daemon
2016-12-06 5:39 ` bugzilla-daemon
2016-12-06 12:02 ` bugzilla-daemon
2016-12-06 12:38 ` bugzilla-daemon
2016-12-06 13:20 ` bugzilla-daemon
2016-12-06 14:45 ` bugzilla-daemon
2019-09-18 19:40 ` 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-98964-502-uBLK4Wsv2Z@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;
as well as URLs for NNTP newsgroup(s).