https://bugs.freedesktop.org/show_bug.cgi?id=61349
Priority: medium Bug ID: 61349 Keywords: regression Assignee: dri-devel@lists.freedesktop.org Summary: [r300g, bisected] piglit rgtc-teximage-01 fails Severity: normal Classification: Unclassified OS: All Reporter: pavel.ondracka@email.cz Hardware: Other Status: NEW Version: git Component: Drivers/Gallium/r300 Product: Mesa
./bin/rgtc-teximage-01 -auto r300: DRM version: 2.24.0, Name: ATI RV530, ID: 0x71c5, GB: 1, Z: 2 r300: GART size: 509 MB, VRAM size: 256 MB r300: AA compression RAM: YES, Z compression RAM: YES, HiZ RAM: YES Got bad R channel reading back 0x8dbb as 0x1908 Got bad R channel reading back 0x8dbc as 0x1908 PIGLIT: {'result': 'fail' }
first bad commit: commit ea63491629f48099371f725e7c3779f2982d7a52 Author: Marek Olšák maraeo@gmail.com Date: Thu Feb 7 04:36:33 2013 +0100
st/mesa: accelerate glGetTexImage for all formats using a blit
This commit allows using glGetTexImage during rendering and still maintain interactive framerates.
This improves performance of WarCraft 3 under Wine. The framerate is improved from 25 fps to 39 fps in the main menu, and from 0.5 fps to 32 fps in the game.
v2: fix choosing the format for decompression
GPU:RV530 Mesa: 2fa9e4c97cd7580010a8aa2eb3026e8f2bdb0035 Kernel: 3.7.3-101.fc17.i686
https://bugs.freedesktop.org/show_bug.cgi?id=61349
--- Comment #1 from Marek Olšák maraeo@gmail.com --- RGTC1 texturing uses only 4 bits of precision in R500, which can cause some piglit failures. If you run the test, you'll see how the precision affects the filtered texture. If it's not completely wrong, let's just say this is a hardware limitation.
https://bugs.freedesktop.org/show_bug.cgi?id=61349
--- Comment #2 from Pavel Ondračka pavel.ondracka@email.cz --- (In reply to comment #1)
RGTC1 texturing uses only 4 bits of precision in R500, which can cause some piglit failures. If you run the test, you'll see how the precision affects the filtered texture. If it's not completely wrong, let's just say this is a hardware limitation.
Yeah, the pictures before and after patch looks almost similar, so probably indeed a precision bug, dunno why it passed before though.
https://bugs.freedesktop.org/show_bug.cgi?id=61349
Marek Olšák maraeo@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED
--- Comment #3 from Marek Olšák maraeo@gmail.com --- Closing, because it's a hardware limitation.
https://bugs.freedesktop.org/show_bug.cgi?id=61349
Marek Olšák maraeo@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |NOTABUG
dri-devel@lists.freedesktop.org