From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 29726] New CRTC ID query breaks Radeon DRM in Zaphod mode
Date: Sat, 18 Sep 2010 16:21:02 -0700 (PDT) [thread overview]
Message-ID: <20100918232102.34139130061@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-29726-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=29726
--- Comment #3 from James Le Cuirot <chewi@aura-online.co.uk> 2010-09-18 16:21:02 PDT ---
I have now tested with two monitors, once in "clone" mode and once in "big
desktop" mode and the behaviour is the same as with a single monitor. Just the
occasional flicker. This is definitely related to Zaphod mode.
The problem still present on linux-next-20100917. Please guys, at least explain
the context surrounding this code and where it would be called from. I've seen
some other odd behaviour that could potentially be related to this and it's
really starting to bug me.
--
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:[~2010-09-18 23:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-21 15:36 [Bug 29726] New: New CRTC ID query breaks Radeon DRM in Zaphod mode bugzilla-daemon
2010-08-21 15:37 ` [Bug 29726] " bugzilla-daemon
2010-08-21 15:45 ` bugzilla-daemon
2010-08-28 14:42 ` bugzilla-daemon
2010-09-18 23:21 ` bugzilla-daemon [this message]
2010-10-24 15:31 ` bugzilla-daemon
2010-10-24 15:33 ` bugzilla-daemon
2010-10-24 23:03 ` bugzilla-daemon
2010-10-25 5:09 ` bugzilla-daemon
2010-10-25 9:11 ` bugzilla-daemon
2010-10-28 1:13 ` bugzilla-daemon
2010-10-28 2:48 ` bugzilla-daemon
2010-10-28 10:25 ` bugzilla-daemon
2011-01-06 23:54 ` 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=20100918232102.34139130061@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 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).