From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 31400] New: [RV740] Mipmapping broken in drm-radeon-next / drm-next
Date: Thu, 4 Nov 2010 17:11:22 -0700 (PDT) [thread overview]
Message-ID: <bug-31400-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=31400
Summary: [RV740] Mipmapping broken in drm-radeon-next /
drm-next
Product: DRI
Version: DRI CVS
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: liquid.acid@gmx.net
Hey there,
I already partially explained this in bug #31046.
With a recent drm-radeon-next or also drm-next the mipmaps are broken with both
r600c and r600g.
My hardware:
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon HD 4770 [RV740]
libdrm, xf86-video-ati and mesa are all git master tip.
Today I found some time to bisect drm-next and this commit introduces the
mipmap issue:
881fe6c1d06bf49f4ab7aef212cdaf66bd059614
drm/radeon/kms: properly compute group_size on 6xx/7xx
Needed for tiled surfaces.
-------------------------------
Link:
http://git.kernel.org/?p=linux/kernel/git/airlied/drm-2.6.git;a=commit;h=881fe6c1d06bf49f4ab7aef212cdaf66bd059614
Looks like tiling_group_size has to be 256 on my hardware.
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:[~2010-11-05 0:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-05 0:11 bugzilla-daemon [this message]
2010-11-08 17:12 ` [Bug 31400] [RV740] Mipmapping broken in drm-radeon-next / drm-next bugzilla-daemon
2010-11-08 18:54 ` bugzilla-daemon
2010-11-09 19:15 ` bugzilla-daemon
2010-11-09 21:10 ` bugzilla-daemon
2010-11-09 21:14 ` bugzilla-daemon
2010-11-18 18:01 ` 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-31400-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox