| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Conflicts:
src/gallium/drivers/svga/svga_screen_texture.c
src/gallium/state_trackers/xorg/xorg_composite.c
src/gallium/state_trackers/xorg/xorg_exa.c
src/gallium/state_trackers/xorg/xorg_renderer.c
src/gallium/state_trackers/xorg/xorg_xv.c
src/mesa/main/texgetimage.c
src/mesa/main/version.h
|
| | |
|
| |\
| | |
| | |
| | |
| | |
| | |
| | | |
Conflicts:
progs/util/shaderutil.c
src/mesa/drivers/dri/r600/r600_context.c
src/mesa/main/version.h
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Support still isn't completely correct, but it's better. piglit
point-sprite now passes. However, glean's pointSprite test fails. In
that test the texture on the sprite is somehow inverted as though
GL_POINT_SPRITE_COORD_ORIGIN were set to GL_LOWER_LEFT. i915 hardware
shouldn't be able to do that!
I believe there are also problems when not all texture units have
GL_COORD_REPLACE set. The hardware enable seems to be all or nothing.
Fixes bug #25313.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This enum is only supported for OpenGL 2.0. If a driver supports
OpenGL 1.4 and GL_ARB_point_sprite, using this enum should generate an
error. This is important because, for example, i915 and i830 can
support GL_ARB_point_sprite, but they cannot support
GL_POINT_SPRITE_COORD_ORIGIN.
This commit just removes the check for NV_point_sprite, which is
completely wrong, and add some comments describing what the code
should do. I don't see an easy way to check for version >= 2.0 from
inside Mesa. Perhaps we should add an extension
GL_MESA_point_sprite_20 (like Intel's old GL_EXT_packed_pixels_12) to
indicate that this added bit of functionality is available.
Also note that glean's pointSprite test only checks for
GL_ARB_point_sprite before trying to use
GL_POINT_SPRITE_COORD_ORIGIN. Naturally, that fails on
non-2.0 implementations (i.e., Mac OS X on GMA 950).
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Thanks to Intel code which I've just stolen pretty much as usual.
This fixes fdo bug 22851 which is a dri1 regression since rewrite.
Tested by: fpiobaf (Fabio) on #radeon
Signed-off-by: Dave Airlie <[email protected]>
|
| | |
| | |
| | |
| | |
| | |
| | | |
This fixes an assertion failure in _mesa_MapBufferARB.
Fixes bugzilla #25253.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Too bad I didn't realize earlier how easy this could be...
Fixes http://bugs.freedesktop.org/show_bug.cgi?id=22767 .
|
| | |
| | |
| | |
| | |
| | |
| | | |
Fixes `xlib' driver build on AIX.
Signed-off-by: Brian Paul <[email protected]>
|
| | |
| | |
| | |
| | | |
It's not implemented yet. fixes fdo bug 24047
|
| | |
| | |
| | |
| | |
| | |
| | | |
This reverts commit 284a7af274bc148f112bd0ebb40583923ee26b49.
This breaks kde desktop effects. See fdo bug 24131
|
| | | |
|
| | |
| | |
| | |
| | | |
(cherry picked from master, commit e9d6ab72be065becf7a077c33919d37faa8db92e)
|
| | |
| | |
| | |
| | |
| | | |
_mesa_TexParameterf calls set_tex_parameterf, which uses the params
argument as an array.
|
| | |
| | |
| | |
| | |
| | | |
_mesa_TexParameterf calls set_tex_parameteri, which uses the params
argument as an array.
|
| | |
| | |
| | |
| | |
| | | |
Simplify gl image level <-> miptree level mapping (are equal now).
Don't allocate miptree for images that won't fit in it (fixes #25230).
|
| | |
| | |
| | |
| | | |
miptrees
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
_mesa_TexGenf calls _mesa_TexGenfv, which uses the params argument
as an array.
|
| | |
| | |
| | |
| | |
| | | |
_mesa_TexGeni calls _mesa_TexGeniv, which uses the params argument
as an array.
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
_mesa_TexEnvf calls _mesa_TexEnvfv, which uses the param argument
as an array.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
Basically don't round up shared textures. This fixes compiz,
but I'm afraid that rounding up texture sizes here in the driver
is doomed, as it will inevitably break texture wrap modes.
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
This reverts commit 124ae596806f1a77af46f1f0e446d448da6e953a.
Pushed by mistake
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
I'm not sure if this is a great change, but helps with caching.
Probably we want to turn this on/off on a driver-by-driver basis.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This helps improve the surface cache behaviour in the face of the
large number of single-use render targets generated by EXA and the xorg
state tracker. Without this we can reference hundreds of individual
render targets from a command buffer, which leaves little scope for
sharing or reuse of those targets.
Flushing early means we can start reusing textures much sooner.
This shouldn't have much effect on normal 3d rendering as it's pretty
rare to have a command buffer with >8 different render targets in that
world.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
Can give a little boost e.g. for anti-aliased text rendering.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Fixes 3D apps not updating with a non-GL compositing manager and Option
"2DAccel" "off".
Also clean up a little pixmap vs. drawable mess.
|
| | | |
|
| | |
| | |
| | |
| | | |
This directory needs indent run over it.
|
| | |
| | |
| | |
| | |
| | | |
Accidentally committed in 7fbdbad5c02e3d5bfbf0e641e2aec224e39fa974
('st/xorg: consolidate some dest surface state setting')
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Similar to the classic swapbuffer throttling in GL drivers, put an
upper bound on the number of outstanding chunks of rendering the state
tracker can generate -- where calling the block handler denotes a
chunk.
Currently that number is set at around 4 "chunks", but could be
tweaked up or down. If a better measure for the amount of outstanding
rendering is found, that would be fine too.
As it stands, this improves interactivity by preventing the X server
from queueing up arbitary amounts of rendering.
|