| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
the destroy path was doing bad things with structure names, make it do less
bad things, use container_of instead
|
| |
|
|
|
|
| |
this is just more code cleanup for old dead code
|
| |
|
|
|
|
|
| |
this is whole texture dirty bit is probably not needed with the current
codebase, need to revisit
|
|
|
|
| |
This replaces a miptree if it won't distrub anything else.
|
| |
|
|
|
|
|
| |
The radeon legacy code want to cleanup not free the texture obj,
so export a function to do that and wrap it.
|
|
|
|
| |
this makes compressed subimages work properly.
|
| |
|
|
|
|
|
| |
You don't need libdrm_radeon for the legacy driver to build,
only for the experimental mm/cs paths.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since texture images are now stored in miptrees, we cannot usually
access them directly via the Data pointer.
So we wrap Mesa's implementation by map/unmap calls.
This crash was triggered by Sauerbraten, Piglit now contains a
regression test.
Signed-off-by: Nicolai Haehnle <[email protected]>
|
|
|
|
|
|
|
|
|
| |
The mip tree creation would crash if the first baselevel image to be uploaded
was not the positive-x image.
Found with Sauerbraten, also added a regression test to Piglit.
Signed-off-by: Nicolai Haehnle <[email protected]>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
R3xx/R5xx fragment program texture constants must come from a hardware
register instead of the constant file, so we redirect if necessary during
the native rewrite phase.
The symptoms of this bug started appearing when the Mesa fixed function
texenvprogram code started using STATE_CURRENT_ATTRIB constants for
texture coordinates when the corresponding attributes were constant across
all vertices.
Signed-off-by: Nicolai Haehnle <[email protected]>
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
tested on r200, texcmp works. May need more verification
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| |
| |
| |
| |
| | |
Conflicts:
configure.ac
src/mesa/drivers/dri/r200/r200_context.c
src/mesa/drivers/dri/r300/r300_render.c
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
While running conform with render-to-texture:
conform -d 33 -v 2 -t -direct
the i965 driver failed this assertion:
intel_clear.c:77: intel_clear_tris: Assertion `(mask & ~((1 << BUFFER_BACK_LEFT) | (1 << BUFFER_FRONT_LEFT) | (1 << BUFFER_DEPTH) | (1 << BUFFER_STENCIL))) == 0' failed.
The problem is that intel_clear_tris() is called by intelClear() to
clear any and all of the available color buffers, but intel_clear_tris()
actually only handles the back left and front left color buffers; so
the assertion fails as soon as you try to clear a non-standard color
buffer.
The fix is to have intelClear() only call intel_clear_tris() with
buffers that intel_clear_tris() can support. intelClear() already backs
down to _swrast_Clear() for all buffers that aren't handled explicitly.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Omit math/m_xform.c from gallium builds since it's not used and it's the
one place we were pulling in the Mesa x86 codegen which collides with
gallium's x86 codegen.
Can now omit ASM_C_SOURCES from gallium build too.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Only VBO uses the evaluator code so call _math_init_eval() there.
Only TNL uses the transform/translate code so call _math_init_transformation()
and _math_init_translate9) there.
This is a step toward resolving some symbol collisions between Mesa's and
gallium's x86 codegen.
Have VBO and TNL modules call _math_init_transformation()
|
| |
| |
| |
| |
| |
| |
| |
| | |
With the pixman CFLAGS at the beginning of the command line, my build
was picking up the glcore.h from glproto, which doesn't have any of the
TFP fields in __GLcontextmodes.
Signed-off-by: Dan Nicholson <[email protected]>
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
Arrays of sampler vars haven't been tested much and might actually be broken.
Will need to be revisited someday.
Another fix for bug 20056.
|
| |
| |
| |
| |
| |
| |
| | |
location = -1 is silently ignored, but other negative values should raise
an error.
Another fix for bug 20056.
|
| |
| |
| |
| | |
intermediate array
|
| |
| |
| |
| |
| |
| |
| | |
If too many array elements are specified, they're to be silently ignored (don't
raise a GL error).
Fixes another issue in bug 20056.
|
| |
| |
| |
| | |
Fixes one of the issues in bug 20056.
|
| |
| |
| |
| |
| | |
Signed-off-by: Johannes Engel <[email protected]>
Acked-by: Jakob Bornecrantz <[email protected]>
|
| |
| |
| |
| | |
snprint symbol does not exist in Windows.
|
| |
| |
| |
| |
| | |
I wonder why we need this... It is only necessary for the MSVC build.
MinGW does not require them.
|
| | |
|