| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Bug #24435
(cherry picked from commit d56125a298106d81e10674f1c4b3b43b51a5139d)
|
|
|
|
| |
This fixes the second part of bug 23552.
|
|
|
|
|
|
| |
Use src->draw_offset intead of zero. Zero usually worked, except when
the src renderbuffer is actually a texture mipmap level higher than zero.
Fixes progs/test/blitfb.c test.
|
|
|
|
| |
A slightly modified version of a patch from Vinson Lee.
|
|
|
|
| |
Bug #24734.
|
| |
|
|
|
|
|
|
|
|
|
| |
This reverts commit 8810b8f67135185d1044746bb861fe2ff997626c.
It turns out the i965 driver uses the intel->Fallback field as a boolean,
not as a bitmask. The intelFallback() function is a no-op in the i965
driver. It would have been nice if there were some comments about this.
I'll fix that next...
|
|
|
|
| |
This would only be hit if we got and invalid index_size.
|
|
|
|
|
|
|
| |
Need to push texture state and polygon state too.
Fixes rendering glitches seen in progs/demos/engine when changing
the rendering mode (wireframe, texture modes).
This makes bitmap rendering a little slower, unfortunately.
|
|
|
|
|
| |
The texture format should not be checked until validation time since
the format might be changed by a subsequent glTexImage() call.
|
| |
|
|
|
|
|
|
|
|
|
| |
By just using offsets, we confused the hardware's tiling calculations,
resulting in failures in miptree validation and blit clears.
Fixes piglit fbo-clearmipmap.
Bug #23552. (automatic mipmap generation)
|
|
|
|
|
| |
Need to return the actual compressed format when the user originally
requested a generic compressed format.
|
|
|
|
|
|
| |
Maps a compressed MESA_FORMAT_x to correspding GLenum. Needed for
querying a texture's actual format when a generic format was originally
requested.
|
| |
|
|
|
|
|
|
|
|
| |
Array indexes are invalid when >= the maximum, but array sizes are
only in valid when > the maximum. This prevented programs from
declaring a single maximum size array.
See the piglit vp-max-array test.
|
|
|
|
|
| |
Per the GLX spec, when changing rendering contexts, the old context
should first be flushed.
|
|
|
|
|
|
|
| |
According to the GLXDestroyContext() man page, the context should not
immediately be destroyed if it's bound to some thread. Wait until it's
unbound to really delete it. The code for doing the later part is
already present in MakeContextCurrent() so no change was needed there.
|
| |
|
|
|
|
|
|
|
|
| |
Setting intel->Fallback = 1 clobbered any fallback state that was already
set. Not sure where this hack originated (the git history is a little
convoluted). Define and use a new BRW_FALLBACK_DRAW bit instead. This
shouldn't break anything and could potentially fix some bugs (but no
specific ones are known).
|
| |
|
| |
|
| |
|
|
|
|
|
| |
The value was probably wrong too.
It was the same as INTEL_FALLBACK_DRAW_BUFFER.
|
|
|
|
| |
otherwise
|
|
|
|
|
|
|
| |
Also avoids empty shader for "END" - seems to be somewhat valid fp
Maybe this can be done differently in the future (fake FRAG_RESULT_COLOR
already in Map_Fragment_Program() or is there a way to program the chip
to not hang in case of no exports.
|
| |
|
|
|
|
| |
s/LERP/LRP/
|
|
|
|
|
| |
strtod_l needs the xlocale.h header on Mac OS. It's possible other
non-Linux OSes would need this header too.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The in kernel texture check fails because of both
bit11 flags being set on 16x16 textures. It tuns out
that these bits are still set and not cleared in the
pp_txpitch field of the texture. The attached patch
at least helps for this case on my machine. It clears
the bit 11 from the pitch field if the texture is smaller
and masks out that hight bits on the conventional width
and height field.
Fixes bug 24584
|
|
|
|
|
|
|
|
| |
size was being calculated based on 3 bytes per pixel with 24 bit depth
instead of 4 bytes. This caused corruption in the bottom 25% of objects.
This finishes fixing the menu/text corruption in compiz/kde4.
Signed-off-by: Robert Noland <[email protected]>
|
| |
|
|
|
|
|
|
|
|
|
| |
_mesa_strtod() is used for shader/program parsing where the decimal
point character is always '.' Use strtod_l() with a "C" locale to
ensure correct string->double conversion when the actual locale uses
another character such as ',' for the decimal point.
Fixes bug 24531.
|
|
|
|
|
| |
We need to get the pitch from the texture level we are rendering to,
rather than just using the base texel width.
|
|
|
|
|
|
| |
Report unsupported attributes while I'm here.
Signed-off-by: Robert Noland <[email protected]>
|
|
|
|
| |
Signed-off-by: Robert Noland <[email protected]>
|
|
|
|
| |
Signed-off-by: Robert Noland <[email protected]>
|
|
|
|
|
|
|
|
| |
Setting the wrong bo size resulting in an incomplete
read cache flush when reading the texture. This fixes the
compiz text corruption.
[agd5f: take hw pitch alignment into account]
|
|
|
|
|
| |
need this to properly test with piglit/glean vert/fragprog tests
copied mostly from r300, many thanks to osiris, nha, airlied, others...
|
|
|
|
|
| |
seems I overlooked this when removing hardcoded swizzles for this
one previously
|
| |
|
|
|
|
|
|
|
| |
- KILLGT takes 2 arguments
- arb KIL has no dst register
- add TODO about clause ending but currently piglit fp-kil passes and
does not hang the card
|
|
|
|
|
|
| |
makes blend functions work better
Signed-off-by: Dave Airlie <[email protected]>
|
|
|
|
| |
Signed-off-by: Dave Airlie <[email protected]>
|
|
|
|
| |
Makes doom3 alot nicer..
|
| |
|
|
|
|
| |
See bug 24531.
|
|
|
|
|
|
| |
Again, last valid address, not first invalid address. Fixes regression
in 255e5be265133280293bbfd8b2f9b74b2dec50bb that the kernel now catches
and caused piglit draw_elements_base_vertex to fail.
|
|
|
|
|
|
|
|
| |
It's the address of the last valid byte, not the address of the first
invalid byte.
This should also fix problems with rendering with the new sanity checks in
the kernel.
|
|
|
|
|
|
|
|
|
|
| |
This change silenced valgrind warnings but broke progs/tests/drawbuffers.
The problem is we don't know the surface's state when we start caching it
(it may or may not be initialized/cleared/etc). So "clearing" it here was
presumptuous. Leaving the code in place (but disabled) for reference and
when using valgrind.
Fixes bug 24401
|