From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 24462] r600: spread spectrum: flickering screen (bisected)
Date: Thu, 9 Dec 2010 20:12:10 GMT [thread overview]
Message-ID: <201012092012.oB9KCAc7013365@demeter1.kernel.org> (raw)
In-Reply-To: <bug-24462-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=24462
--- Comment #9 from Luca Tettamanti <kronos.it@gmail.com> 2010-12-09 20:12:05 ---
(In reply to comment #8)
> This patch disables use of the ss fixed ref divide and should fix it.
Yes, taking out that code worked. I'm of course available for further testing
if you're not satisfied with this workaround ;)
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
next prev parent reply other threads:[~2010-12-09 20:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-08 16:18 [Bug 24462] New: r600: spread spectrum: flickering screen (bisected) bugzilla-daemon
2010-12-08 17:11 ` [Bug 24462] " bugzilla-daemon
2010-12-08 20:27 ` bugzilla-daemon
2010-12-08 20:39 ` bugzilla-daemon
2010-12-08 20:47 ` bugzilla-daemon
2010-12-08 21:14 ` bugzilla-daemon
2010-12-08 22:12 ` bugzilla-daemon
2010-12-08 22:32 ` bugzilla-daemon
2010-12-08 23:05 ` bugzilla-daemon
2010-12-09 20:12 ` bugzilla-daemon [this message]
2010-12-17 0:43 ` bugzilla-daemon
2010-12-20 6:57 ` bugzilla-daemon
2010-12-29 22:48 ` bugzilla-daemon
2011-02-11 6:57 ` bugzilla-daemon
2011-02-11 7:32 ` bugzilla-daemon
2011-02-11 16:09 ` bugzilla-daemon
2011-02-12 1:17 ` bugzilla-daemon
2011-02-14 13:56 ` 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=201012092012.oB9KCAc7013365@demeter1.kernel.org \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.sourceforge.net \
/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).