From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 15186] Radeon KMS: [RV730] Garbled kwin shadows and pixmaps
Date: Wed, 3 Feb 2010 13:18:45 GMT [thread overview]
Message-ID: <201002031318.o13DIjtB006081@demeter.kernel.org> (raw)
In-Reply-To: <bug-15186-2300@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=15186
--- Comment #14 from Nils Kneuper <crazy-ivanovic@gmx.net> 2010-02-03 13:18:43 ---
(In reply to comment #8)
> Applied second patch on top of vanilla 2.6.33-rc6:
> - Both #if 1's: *Fixed*
> - set_domain #if 0, wait_idle #if 1: *Fixed*
> - set_domain #if 1, wait_idle #if 0: *Not fixed* (same effect as before)
>
> The wait_idle part seems important.
Okay, after my tests with 2.6.33-rc6 I do have exactly the same results! So the
"wait_idle #if 1" part of the patch basically does the trick. Just to be 100%
sure I checked if the issues do occur with vanilla 2.6.32, too, and they are
there just as with an unpatched 2.6.33-rc6 for me. So it might in fact be that
the "real" issue (at least for me) is something else but the change strangely
does fix things.
As a note on the side: it makes no difference if qt 4.5.x or 4.6.x is used, had
the issues with both.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
--
next prev parent reply other threads:[~2010-02-03 13:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-31 11:56 [Bug 15186] New: Radeon KMS: [RV730] Garbled kwin shadows and pixmaps bugzilla-daemon
2010-01-31 11:58 ` [Bug 15186] " bugzilla-daemon
2010-01-31 11:59 ` bugzilla-daemon
2010-01-31 12:13 ` bugzilla-daemon
2010-02-01 11:50 ` bugzilla-daemon
2010-02-01 18:49 ` bugzilla-daemon
2010-02-01 21:14 ` bugzilla-daemon
2010-02-02 12:58 ` bugzilla-daemon
2010-02-02 18:54 ` bugzilla-daemon
2010-02-02 21:43 ` bugzilla-daemon
2010-02-02 22:28 ` bugzilla-daemon
2010-02-02 23:05 ` bugzilla-daemon
2010-02-03 9:21 ` bugzilla-daemon
2010-02-03 12:11 ` bugzilla-daemon
2010-02-03 13:18 ` bugzilla-daemon [this message]
2010-02-03 21:14 ` bugzilla-daemon
2010-02-04 11:26 ` bugzilla-daemon
2010-02-04 16:15 ` bugzilla-daemon
2010-02-04 18:03 ` bugzilla-daemon
2010-02-04 18:38 ` bugzilla-daemon
2010-02-04 19:00 ` bugzilla-daemon
2010-02-07 10:59 ` bugzilla-daemon
2010-02-07 11:33 ` 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=201002031318.o13DIjtB006081@demeter.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 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.