From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 33824] New: [r600g, tiling] mipmap rendering errors / block artifacts
Date: Tue, 1 Feb 2011 13:22:45 -0800 (PST) [thread overview]
Message-ID: <bug-33824-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=33824
Summary: [r600g, tiling] mipmap rendering errors / block
artifacts
Product: DRI
Version: DRI CVS
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: liquid.acid@gmx.net
Hi there,
this is a update of bug #31046, where the main issue was GPU resets caused by
enabling tiling (R600_FORCE_TILING=1) with the r600g driver.
The situation however was changed, and now R600_FORCE_TILING only causes mipmap
rendering errors in a few application. Last time I tested ioquake3, doom3
(demo) and both ut2003 and ut2004.
ut03 and ut04 are still affected by the blocky rendering errors (see the other
bug for screenshots illustrating the problem), but both ioquake3 and doom3 now
look perfectly fine.
My hardware:
ATI Technologies Inc Radeon HD 4770 [RV740]
libdrm, mesa and xf86-video-ati are all git master tip.
ColorTiling is enabled in the xorg.conf, verified this by checking the Xorg
logfile.
kernel is d-r-t
Greets,
Tobias
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-02-01 21:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-01 21:22 bugzilla-daemon [this message]
2011-02-02 2:54 ` [Bug 33824] [r600g, tiling] mipmap rendering errors / block artifacts bugzilla-daemon
2011-05-07 0:26 ` bugzilla-daemon
2011-05-07 12:07 ` bugzilla-daemon
2011-05-07 13:07 ` bugzilla-daemon
2011-05-07 16:14 ` bugzilla-daemon
2011-05-09 3:05 ` bugzilla-daemon
2011-05-12 0:04 ` bugzilla-daemon
2011-05-12 0:09 ` bugzilla-daemon
2011-05-12 0:22 ` 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=bug-33824-502@http.bugs.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.