Age | Commit message (Collapse) | Author |
|
|
|
No benefits yet.
|
|
|
|
|
|
Otherwise a CS is refused by kernel 2.6.31 (and maybe all later
versions, not sure).
|
|
|
|
Just make it cover the whole framebuffer in that case. Otherwise the kernel CS
checker may complain, e.g. running progs/demos/gearbox. That runs fast now
here, but doesn't look right yet.
|
|
There's like five good reasons for this, I swear.
|
|
Instead of vs_tab, we use vs_output_tab and it's local now. fs_tab hasn't
been used anywhere, so I removed it and r300_update_fs_tab too.
|
|
These now work:
piglit/lodclamp
piglit/levelclamp
|
|
From the SW TCL fixups.
|
|
And some other fixes.
|
|
|
|
Signed-off-by: Corbin Simpson <MostAwesomeDude@gmail.com>
|
|
Signed-off-by: Corbin Simpson <MostAwesomeDude@gmail.com>
|
|
Cleared out my git stash.
|
|
|
|
|
|
Mipmaps not tested. Also, I am not sure why piglit/texturing/tex3d needs
to have color tolerance +-1 to pass. The classic Mesa driver doesn't
need that.
|
|
Part of the fastpath cleanup.
|
|
|
|
|
|
|
|
Need to move rs_block to this, too.
Also, I'm getting massive amounts of flicker for some reason; I bet we've gotta
re-re-examine PSC and friends. :C
|
|
It may seem pointless, but this avoids a fair amount of predicted CSO pain.
|
|
I missed this, thanks to Corbin for pointing it out.
|
|
Add support for begin/end in each CS so we don't get any other
processes rendering in between.
TODO:
blame other parts of driver for this not working like Z.
|
|
This means we don't emit in the begin query but when we have
to flush. Similiar to classic.
TODO:
make query object actually work.
|
|
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.
|
|
|
|
It gets really annoying watching r300g tell me how it's filling surfaces.
Or falling back during filling surfaces.
|
|
Individual texture images have a stride, but textures as a whole do not.
There are still pieces of code which are confused about this, but the core of
the confusion is hopefully gone.
Signed-off-by: Nicolai Hähnle <nhaehnle@gmail.com>
|
|
Seriously guys....
|
|
So that debugging is no longer a full-spam-or-nothing approach, you are now
supposed to set the RADEON_DEBUG environment flag just like for classic Mesa.
The available debug flags are different, however. Just running an OpenGL
application with RADEON_DEBUG set to an arbitrary string will print out
helpful information.
Everything must be compiled with -DDEBUG for any of this to work
|
|
Still broken, but compiles cleaner, behaves better, etc.
|
|
Not needed with new compiler.
|
|
This is entirely untested on R500, and needs more testing on R300.
|
|
|
|
Signed-off-by: Corbin Simpson <MostAwesomeDude@gmail.com>
|
|
Signed-off-by: Corbin Simpson <MostAwesomeDude@gmail.com>
|
|
Appart from separating r3xx/r5xx fragment shaders, a more consistent
naming scheme has been applied. From now on:
r300 = all chips
r3xx = R300/R400 only
r5xx = R500 only
This way r300_fragment_shader is the master struct, and the structs
r3xx_fragment_shader and r5xx_fragment_shader inherits it.
|
|
|
|
Less briefly... Shaders need to be recompiled if their constantbuf
offsets have changed. However, since we only change them from shaders if
immediates need to be emitted, we shouldn't bother if the shader doesn't
use immediates.
|
|
Still not correct, but really I don't care.
|
|
This makes glxgears draw properly with SW TCL.
|
|
Still broken...
|
|
We'll just forever leave it in r300_winsys.h since it's needed for
whichever winsys is hosting the pipe.
|
|
|
|
|
|
|