From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 33042] New: RV770: Broken Mipmap creation/display
Date: Wed, 12 Jan 2011 17:23:51 -0800 (PST) [thread overview]
Message-ID: <bug-33042-502@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=33042
Summary: RV770: Broken Mipmap creation/display
Product: DRI
Version: unspecified
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel@lists.freedesktop.org
ReportedBy: andreas.bombe@mytum.de
Created an attachment (id=41946)
--> (https://bugs.freedesktop.org/attachment.cgi?id=41946)
Celestia screenshot
I'm using mainline Linux kernels, and this bug is a regression from 2.6.36. It
got broken already in 37-rc series but I haven't noticed it (compiz desktop
works fine) and didn't get around to report it in time.
The latest kernel I've tested is 2.6.37-05292-g7bc4a4c running Debian sid.
It appears that the vertical size assumed during display of the mipmap is twice
the mipmap's height. See attached screenshot from Celestia which shows the
first level mipmap on the central star. Horizontal size seems to be correct.
Zooming outward reveals further mipmap levels with unrelated data as can be
seen on the other two stars in the image.
--
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-01-13 1:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-13 1:23 bugzilla-daemon [this message]
2011-01-13 1:25 ` [Bug 33042] RV770: Broken Mipmap creation/display bugzilla-daemon
2011-01-13 1:29 ` bugzilla-daemon
2011-01-13 2:59 ` bugzilla-daemon
2011-03-08 17:55 ` 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-33042-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.