From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 28771] [RADEON:KMS::R300C:R300G] waiting for vline forced always on
Date: Mon, 21 Feb 2011 16:22:38 -0800 (PST) [thread overview]
Message-ID: <20110222002238.DA16A130009@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-28771-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=28771
--- Comment #33 from Sven Arvidsson <sa@whiz.se> 2011-02-21 16:22:38 PST ---
(In reply to comment #32)
> I'm still not sure if toggling vsync on/off inside an application is supposed
> to work (it doesn't seem to with r300g in Sauerbraten or M.A.R.S. for example).
> What component should a bug be filed against in this case?
>
> At least M.A.R.S. seems to be using glXSwapIntervalSGI for vsync.
Actually, forget about this part. It works, at least in MARS. Not sure about
Sauerbraten, but it could be a bug in the game.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2011-02-22 0:22 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-26 19:14 [Bug 28771] New: Vsync always on bugzilla-daemon
2010-06-28 16:31 ` [Bug 28771] " bugzilla-daemon
2010-06-28 20:18 ` bugzilla-daemon
2010-06-28 22:41 ` bugzilla-daemon
2010-07-15 18:55 ` bugzilla-daemon
2010-07-15 19:28 ` bugzilla-daemon
2010-07-15 20:18 ` bugzilla-daemon
2010-07-16 12:03 ` bugzilla-daemon
2010-07-16 13:30 ` bugzilla-daemon
2010-07-16 13:37 ` bugzilla-daemon
2010-07-18 5:36 ` bugzilla-daemon
2010-07-18 8:10 ` bugzilla-daemon
2010-07-18 10:35 ` bugzilla-daemon
2010-07-18 10:50 ` bugzilla-daemon
2010-07-18 12:09 ` bugzilla-daemon
2010-07-18 13:14 ` bugzilla-daemon
2010-07-18 13:22 ` bugzilla-daemon
2010-07-19 17:29 ` bugzilla-daemon
2010-07-28 6:00 ` bugzilla-daemon
2010-07-28 11:41 ` bugzilla-daemon
2010-07-28 13:44 ` bugzilla-daemon
2010-08-15 16:12 ` bugzilla-daemon
2010-08-16 9:45 ` bugzilla-daemon
2010-08-16 9:50 ` bugzilla-daemon
2010-08-18 20:22 ` bugzilla-daemon
2010-08-23 4:37 ` bugzilla-daemon
2010-09-26 21:19 ` bugzilla-daemon
2010-09-27 9:55 ` bugzilla-daemon
2010-10-19 12:45 ` [Bug 28771] Waiting for vline forced " bugzilla-daemon
2010-10-19 12:50 ` bugzilla-daemon
2010-10-22 13:17 ` bugzilla-daemon
2011-02-09 15:40 ` [Bug 28771] [RADEON:KMS::R300C:R300G] waiting " bugzilla-daemon
2011-02-21 21:44 ` bugzilla-daemon
2011-02-21 21:51 ` bugzilla-daemon
2011-02-22 0:03 ` bugzilla-daemon
2011-02-22 0:22 ` bugzilla-daemon [this message]
2011-10-20 8:57 ` bugzilla-daemon
2014-07-07 16:43 ` bugzilla-daemon
2018-06-12 19:09 ` 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=20110222002238.DA16A130009@annarchy.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.