Age | Commit message (Collapse) | Author |
|
|
|
No idea why st/mesa unnecessarily inserts TXP where TEX is sufficient.
Also re-enabling the NPOT fallback for repeat in r300g.
|
|
A variant thereof might be later reintroduced for the mirrored-clamp modes.
|
|
It causes regressions. I haven't tested the MIRROR wrap modes,
so not sure about that..
|
|
These work just fine.
|
|
|
|
texdepth stopped working when npot went in, this brings it back
to life.
< MostAwesomeDude> That looks like what I was going to do.
Signed-off-by: Dave Airlie <airlied@redhat.com>
|
|
This hopefully fixes the crash in the FDO bug #27634, not the bug itself.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* The constant buffer emission is separated from RC state variables emission.
* The immediates are emitted with FS code.
|
|
Better than killing an application.
|
|
* Turn some assertions to error messages.
* At most 16 vertex elements can be set, others are ignored.
* Rasterize at most 8 vertex-shader generic outputs, others are ignored.
This includes fog and WPOS.
* Unknown shader semantic names are ignored.
|
|
The evolution of TX_FORMAT bits is as follows:
* When a texture is created, set bits independent of pipe_format.
* When a sampler view is created, add format-specific bits.
* When sampler states and views are getting merged, add min/max LOD.
|
|
|
|
|
|
We really need to get these into bug reports.
|
|
|
|
|
|
r300compiler doesn't handle half swizzles for vert shaders, which don't
have them. So, for now, disable them.
|
|
|
|
This maybe breaks the vert compiler. Hopefully not.
|
|
|
|
|
|
|
|
The state setups which aren't derived anymore have been moved to the VS
and FS objects.
|
|
|
|
|
|
Signed-off-by: Nicolai Hähnle <nhaehnle@gmail.com>
|
|
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
|
|
|
|
This is entirely untested on R500, and needs more testing on R300.
|
|
Also trust that Gallium will not give us TGSI that miscounts shader consts.
This creates a 20x speedup on glxgears, from 8 FPS to 160 FPS.
|
|
Remove the need to have a pointer in this struct by just including
the immediate data inline. Having a pointer in the struct introduces
complications like needing to alloc/free the data pointed to, uncertainty
about who owns the data, etc. There doesn't seem to be a need for it,
and it is unlikely to make much difference plus or minus to performance.
Added some asserts as we now will trip up on immediates with more
than four elements. There were actually already quite a few such asserts,
but the >4 case could be used in the future to specify indexable immediate
ranges, such as lookup tables.
|
|
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.
|