From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 30960] [r300g][glsl][libtxc_dxtn] Texture corruption in Xonotic with lightmaps
Date: Mon, 25 Oct 2010 01:14:35 -0700 (PDT) [thread overview]
Message-ID: <20101025081435.B2DF013004E@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-30960-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=30960
--- Comment #41 from Michel Dänzer <michel@daenzer.net> 2010-10-25 01:14:35 PDT ---
(In reply to comment #39)
> Not necessary, it's just a theory. It would be interesting to rewrite that
> function to use the 3D engine on r300 and see if it fixes anything.
A simpler test could be to use r200_copy_dma instead of r100_copy_blit for the
.copy hook in radeon_asic.c. (On my mobile RV350 that seems to perform better
anyway...)
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2010-10-25 8:14 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-18 12:42 [Bug 30960] New: [r300g][glsl] Texture corruption in Xonotic with lightmaps bugzilla-daemon
2010-10-18 12:45 ` [Bug 30960] " bugzilla-daemon
2010-10-18 12:46 ` bugzilla-daemon
2010-10-18 21:26 ` bugzilla-daemon
2010-10-18 21:36 ` bugzilla-daemon
2010-10-18 22:54 ` bugzilla-daemon
2010-10-18 22:55 ` bugzilla-daemon
2010-10-18 22:56 ` bugzilla-daemon
2010-10-18 23:03 ` bugzilla-daemon
2010-10-19 3:51 ` bugzilla-daemon
2010-10-19 16:16 ` bugzilla-daemon
2010-10-19 16:17 ` bugzilla-daemon
2010-10-19 16:20 ` bugzilla-daemon
2010-10-19 16:21 ` bugzilla-daemon
2010-10-19 16:22 ` bugzilla-daemon
2010-10-19 16:23 ` bugzilla-daemon
2010-10-19 16:24 ` bugzilla-daemon
2010-10-19 16:25 ` bugzilla-daemon
2010-10-19 16:33 ` bugzilla-daemon
2010-10-19 16:34 ` bugzilla-daemon
2010-10-19 16:35 ` bugzilla-daemon
2010-10-19 16:35 ` bugzilla-daemon
2010-10-19 16:40 ` bugzilla-daemon
2010-10-19 16:50 ` bugzilla-daemon
2010-10-19 16:51 ` bugzilla-daemon
2010-10-19 16:51 ` bugzilla-daemon
2010-10-19 16:52 ` bugzilla-daemon
2010-10-20 6:42 ` bugzilla-daemon
2010-10-20 19:54 ` bugzilla-daemon
2010-10-20 19:57 ` bugzilla-daemon
2010-10-24 1:38 ` bugzilla-daemon
2010-10-24 12:28 ` bugzilla-daemon
2010-10-24 12:31 ` bugzilla-daemon
2010-10-24 12:32 ` bugzilla-daemon
2010-10-24 12:33 ` bugzilla-daemon
2010-10-24 12:33 ` bugzilla-daemon
2010-10-24 12:33 ` bugzilla-daemon
2010-10-24 12:34 ` bugzilla-daemon
2010-10-24 12:50 ` bugzilla-daemon
2010-10-24 16:32 ` bugzilla-daemon
2010-10-24 20:08 ` bugzilla-daemon
2010-10-24 20:09 ` [Bug 30960] [r300g][glsl][libtxc_dxtn] " bugzilla-daemon
2010-10-24 20:16 ` bugzilla-daemon
2010-10-24 20:50 ` bugzilla-daemon
2010-10-24 21:00 ` bugzilla-daemon
2010-10-24 22:27 ` bugzilla-daemon
2010-10-24 22:31 ` bugzilla-daemon
2010-10-24 22:38 ` bugzilla-daemon
2010-10-25 5:16 ` bugzilla-daemon
2010-10-25 8:14 ` bugzilla-daemon [this message]
2010-10-25 20:42 ` bugzilla-daemon
2010-10-25 21:14 ` bugzilla-daemon
2010-10-25 21:15 ` bugzilla-daemon
2010-10-26 7:31 ` bugzilla-daemon
2010-10-26 8:29 ` 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=20101025081435.B2DF013004E@annarchy.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.