From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 28359] New: Regression running Second Life viewer on r600 (mipmap generation issue?)
Date: Wed, 2 Jun 2010 11:29:48 -0700 (PDT) [thread overview]
Message-ID: <bug-28359-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=28359
Summary: Regression running Second Life viewer on r600 (mipmap
generation issue?)
Product: Mesa
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/R600
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: makosoft@googlemail.com
There's a regression in recent git master when running the Second Life viewer
on the r600 driver. Objects flash in and out of existence continuously, making
Second Life unusable. git bisect points to the commit
055750fafba58fd2ee0f5611b566a71ab0f22984 "Enable hardware mipmap generation for
radeon" on the 24th of May, which is plausible since Second Life generates all
mipmaps at runtime.
I'm using a 2600XT card, Linux 2.6.34, latest libdrm master, and the latest
unofficial Imprudence client release (since the official client isn't available
in an x86_64 version).
--
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-06-02 18:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-02 18:29 bugzilla-daemon [this message]
2010-06-02 19:21 ` [Bug 28359] Regression running Second Life viewer on r600 (mipmap generation issue?) bugzilla-daemon
2010-06-03 10:39 ` bugzilla-daemon
2010-06-20 11:50 ` bugzilla-daemon
2012-11-02 16:28 ` bugzilla-daemon
2012-11-02 17:17 ` bugzilla-daemon
2012-11-02 17:42 ` 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-28359-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;
as well as URLs for NNTP newsgroup(s).