| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
See bug 24217.
|
|
|
|
|
| |
This silences tons of valgrind warnings in programs that don't call
glClear(), such as progs/demos/gamma.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Nasty bug when the surface is freed and another is allocated right on
top of it. The next time we set the fb state SP thinks it's the same
surface and doesn't flush, and when the flush eventually happens the
surface belongs to a completely different texture.
(cherry picked from commit a77226071f6814a53358a5d6caff685889d0e4ec)
Conflicts:
src/gallium/drivers/softpipe/sp_context.c
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Build was broken by commit 9666529b5a5be1fcde82caadc2fe2efa5ea81e49
I'm not certain that this is entirely the correct fix since the demo
from bug #23774 seemed to work before the commit that broke the build.
Signed-off-by: Robert Noland <[email protected]>
Signed-off-by: Brian Paul <[email protected]>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The main issue is we didn't always have a gallium texture object with
enough space to store the to-be-generated mipmap levels. When that's
the case, allocate a new gallium texture and use st_texure_finalize()
to copy images from the old texture to the new one.
We also had the baseLevel parameter to st_render_mipmap() wrong.
|
| |
| |
| |
| |
| |
| |
| | |
Don't compute the st_texture_object::lastLevel field based on the texture
filters. Use the _MaxLevel value that core Mesa computes for us.
When called from the GenerateMipmap path, we'll use the lastLevel field
as-is.
|
| | |
|
| |
| |
| |
| | |
Bug #23760 (crashes in wine)
|
| |
| |
| |
| | |
Avoids an unnecessary fallback.
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
This fixes the clears in openarena with the new metaops clear code, and
the new piglit vbo-subdata-sync test.
Bug #23857.
|
| |
| |
| |
| |
| | |
Its flagging of extra state that's already flagged by the vtbl new_batch
when appropriate was confusing my tracking down of the OA clear bug.
|
|\| |
|
| | |
|
| |
| |
| |
| |
| | |
At the time of the enable there may not be a Z buffer, but one
may be attached to the FBO later.
|
| |
| |
| |
| |
| |
| |
| | |
If the currently bound FBO isn't yet validated it's possible for
rgbMode to be zero so we'll lose the texture enable.
This could fix some FBO rendering glitches, but I don't know of
any specific instances.
|
| |
| |
| |
| |
| |
| |
| | |
This is similar to what r300 does inside the driver, but I've added it as
a generic option since it seems most hardware will want it.
Fixes piglit nv-init-zero-reg.vpfp and nv-init-zero-addr.vpfp.
|
| | |
|
| | |
|
| |
| |
| |
| | |
This helps let drivers treat NV_vp like ARB_vp.
|
| |
| |
| |
| |
| |
| |
| | |
If there happened to be a bound VBO when intel_generate_mipmap() was
called we blew up because of a bad vertex array pointer.
Fixes regnumonline, bug 23859.
|
| | |
|
| | |
|
| |
| |
| |
| | |
Otherwise some apps will emit tons of warnings.
|
| |
| |
| |
| |
| |
| |
| | |
Radeon generic scissors code had problem that some of code was using exclusive
and some inclusive bottom right corner. Only r600 driver is using exclusive
coordinate so changed generic code to pass inclusive coordinate and r600 driver
changes BR coordinate to be exclusive.
|
|\| |
|
| |
| |
| |
| |
| |
| | |
Mostly fixes progs/demos/lodbias when MESA_TEX_PROG=1. But the LOD still
seems off by -1 or so.
May be an issue with the params passed to _swrast_compute_lambda()
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
In get_array_bounds we were previously defining a user buffer sized as
(nr_vertices * stride). The trouble is that if the vertex data
occupies less than stride bytes, the extra tailing (stride - size)
bytes may extend outside the memory actually allocated by the app and
caused a segfault.
To fix this, define a the buffer bounds to be:
ptr .. ptr + (nr-1)*stride + element_size
|
| |
| |
| |
| | |
This fixes the glean/glsl1 "texture2D(), with bias" test when using SSE.
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
seems to work here ...
|
| |
| |
| |
| | |
128 gprs, 256 reg-based consts
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- max texture size is 8k, but mesa doesn't support
that at the moment.
- attempt to set shader limits to what the hw actually
supports
- clean up some old r300 cruft
- no need to explicitly disable irqs. This is fixed
in the drm now.
Signed-off-by: Alex Deucher <[email protected]>
|
| |
| |
| |
| |
| |
| |
| |
| | |
- MUL_LIT is ALU.Trans instruction
- some Trans instructions can take 3 arguments
- don't clobber dst.x, use dst.z as temp, it'll get written correct
value in last insn
- respect source swizzles
|
| |
| |
| |
| | |
registers takes radius
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
1D tile span support for depth/stencil/color/textures
Z and stencil buffers are always tiled, so this fixes
sw access to Z and stencil buffers. color and textures
are currently linear, but this adds span support when we
implement 1D tiling.
This fixes the text in progs/demos/engine and progs/tests/z*
|
| |
| |
| |
| | |
Noticed by rnoland on IRC.
|
| |
| |
| |
| | |
with some minor updates from Richard.
|