| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
This reverts commit 5325f8624093bb1ec30d581b4ff64218ceab99f9.
|
| |
|
| |
|
|
|
|
|
| |
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.
|
| |
| |
| |
| |
| | |
This involved fixing driConcatConfigs to not return const (which had made a
mess of a previous patch too).
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
Everything other than "make sure the last rendering ends up visible on the
screen" doesn't need that behavior.
|
| | |
|
| |
| |
| |
| | |
Found while debugging cairo-gl.
|
| | |
|
| |\
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This is the big merge of the gallium-0.2 branch into master.
gallium-master-merge was just the staging area for it.
Both gallium-0.2 and gallium-master-merge are considered closed now.
Conflicts:
progs/demos/Makefile
src/mesa/main/state.c
src/mesa/main/texenvprogram.c
|
| | |
| | |
| | |
| | | |
Add the MSAA samples array or make sure its contents are initialized.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
(cherry picked from commit f7d80aa00611917bc8ce637136d982b151b8f44f)
This also involved adding the new MSAA fields to driCreateConfigs().
Also, re-add prog_instructions->Sampler field for i965 driver. Will
have to revisit that.
|
| | |\
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Merge commit 'origin/gallium-0.2' into gallium-master-merge
Conflicts:
Makefile
docs/relnotes-7.4.html
docs/relnotes.html
src/mesa/drivers/dri/i965/brw_wm.h
src/mesa/main/imports.c
src/mesa/main/mtypes.h
src/mesa/main/texcompress.c
src/mesa/main/texenvprogram.c
src/mesa/main/version.h
src/mesa/vbo/vbo_exec_api.c
src/mesa/vbo/vbo_save_draw.c
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Previously, "in-place" swizzles such as:
MOV t, t.xxyx;
were handled incorrectly. Fixed by splitting the one loop into two loops so we
get all the refs before assigning them (to avoid potential clobbering).
(cherry picked from master/commit faa48915d27634a12f123eaa6e954ec79565e365)
|
| | | |
| | | |
| | | |
| | | | |
(cherry picked from master/commit f78c388b6c156cb155f089b00612f00919090a8e)
|