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 12:11:15 GMT [thread overview]
Message-ID: <201002031211.o13CBFNA026929@demeter.kernel.org> (raw)
In-Reply-To: <bug-15186-2300@http.bugzilla.kernel.org/>
http://bugzilla.kernel.org/show_bug.cgi?id=15186
Nils Kneuper <crazy-ivanovic@gmx.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |crazy-ivanovic@gmx.net
--- Comment #13 from Nils Kneuper <crazy-ivanovic@gmx.net> 2010-02-03 12:11:11 ---
I do observe the same issues as the original poster. Though for me the issues
does exist whenever I use KMS. It makes not difference if 2.6.32* (the first
time I tried KMS with my rv670 based card) or 2.6.33-rc6. It makes no
difference if I change acceleration method from OpenGL to XRender.
I have not checked the patch provided in this thread, will do so later on and
check if the issues persist. In general I do guess that it is not a bug in mesa
since without KMS, this issue does not occur. I will get myself rc6, test with
your patch and report back.
System info:
lspci | grep VGA
01:00.0 VGA compatible controller: ATI Technologies Inc RV670PRO [Radeon HD
3850]
Gentoo "unstable" amd64
Linux 2.6.32 up to (at least) 2.6.33-rc5 with Radeon KMS (grub boot param:
radeon.modeset=1)
Mesa git version, master branch
xf86-video-ati git version, master branch
xorg-server-1.7.4.901 (happened with other xorg-server 1.7.x versions, too)
libdrm git version, master branch
KDE 4.3.5 (composite desktop enabled or disabled), same with previous 4.3.x
versions
--
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 12:11 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 [this message]
2010-02-03 13:18 ` bugzilla-daemon
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=201002031211.o13CBFNA026929@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox