| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
r400 fragment shaders now support up to 64 temporary registers,
512 ALU instructions, and 512 TEX instructions.
|
|
|
|
|
|
|
|
|
| |
Really no idea why I didn't see this before, but these values were opposite
the register spec.
this seems to fix rv530 HiZ on my laptop, will reenable in next commit.
Signed-off-by: Dave Airlie <[email protected]>
|
|
|
|
|
|
|
|
|
|
| |
Finished up by Marek Olšák.
We can set the constant space to use a different area per-call to the shader,
we can avoid flushing the PVS as often as we do by spreading out the constants
across the whole constant space.
Signed-off-by: Marek Olšák <[email protected]>
|
|
|
|
|
|
| |
This fixes all S3TC piglit/texwrap tests.
NOTE: This is a candidate for the 7.9 branch.
|
|
|
|
|
|
|
|
|
| |
Even though MIP filtering is not supported, we can bind an arbitrary mipmap
as the zero mipmap level.
NPOT textures now follow GL_TEXTURE_BASE_LEVEL and GL_TEXTURE_MIN_LOD.
This fixes piglit/fbo-copyteximage.
|
|
|
|
| |
Single loops work, but nested loops do not.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This implements fast Z clear, Z compression, and HiZ support for r300->r500
GPUs.
It also allows cbzb clears when fast Z clears are being used for the ZB.
It requires a kernel with hyper-z support.
Thanks to Marek Olšák <[email protected]>, who started this off, and Alex Deucher at AMD for providing lots of hints.
v2:
squashed zmask ram size fix]
squashed r300g/blitter: fix Z readback when compressed]
v3:
rebase around texture changes in master - .1 fix more bits
v4:
migrated to using u_mm in r300_texture to manage hiz/zmask rams consistently
disabled HiZ when using OQ
flush z-cache before turning hyper-z off
update hyper-z state on dsa state change
store depthclearvalue across cbzb clears and replace it afterwards.
Signed-off-by: Dave Airlie <[email protected]>
|
| |
|
| |
|
| |
|
|
|
|
| |
This should fix corrupted texturing on r3xx-r4xx.
|
| |
|
|
|
|
|
| |
This is a secret texture format, do not tell anybody.
And it looks like we can read stencil in the shader too.
|
| |
|
| |
|
|
|
|
| |
In case anyone needs it, it's here.
|
|
|
|
| |
The CS checker already knows about this.
|
|
|
|
|
| |
Oh look, an undocumented feature. It's a nice tool for benchmarking
texturing.
|
|
|
|
|
| |
Signed-off-by: Jeff Smith <[email protected]>
Signed-off-by: Brian Paul <[email protected]>
|
|
|
|
|
|
|
|
|
|
| |
The path for VAP_ALT_NUM_VERTICES is also in place (and tested)
but not enabled by default due to the missing support of this reg
in the upstream kernel.
Also, a non-zero BUFFER_BASE in the INDX_BUFFER packet3 hangs the machine.
Am I missing something? Because of this, only draw_arrays can render
more than 65535 vertices without the use of VAP_ALT_NUM_VERTICES.
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
docs/relnotes.html
src/gallium/drivers/llvmpipe/lp_tex_sample_c.c
src/gallium/drivers/r300/r300_cs.h
src/mesa/drivers/dri/i965/brw_wm_surface_state.c
src/mesa/main/enums.c
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
And reorder fragment shader inputs so that the colors are before texcoords,
as is allocated by the shader compiler. This commit makes VS->FS attribute
routing work on R500.
|
|/
|
|
|
|
| |
These now work:
piglit/lodclamp
piglit/levelclamp
|
| |
|
|
|
|
| |
Also, correct typos in comments.
|
|
|
|
|
|
| |
Signed-off-by: Corbin Simpson <[email protected]>
DSA really needs its head examined someday. ~ C.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1: add rv530 support
- num z pipes cap
- add proper start/finish query options for rv530
2: convert to use linked list properly.
3: add flushing required check.
4: initial Z top disabling support.
TODO:
make it actually work on my rv530.
|
|
|
|
| |
also enable cube/3d bits in txformat reg
|
|
|
|
| |
Still broken, but compiles cleaner, behaves better, etc.
|
|
|
|
| |
(cherry picked from commit 88c01a15da5639dd68a6a0133724994cb66f1316)
|
| |
|
| |
|
|
|
|
| |
What bugs me is that the YUV444 format somehow worked properly. :3
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Sorry, but it's confusing when format0 in r300_reg != format0 in the docs.
|
| |
|