summaryrefslogtreecommitdiff
path: root/src/gallium
AgeCommit message (Collapse)Author
2010-01-31st/egl: Do not ignore configs without a renderable type.Chia-I Wu
Configs without a renderable type are still informative for programs such as eglinfo.
2010-01-31st/egl: Remove egl_g3d_get_current_context.Chia-I Wu
There is now _eglGetAPIContext that can return the current context of the given API.
2010-01-30Revert "r300g: Don't handle SHADOW_AMBIENT."Corbin Simpson
This reverts commit 627a45848faf9e6d19d386b9eb30d36bf18d0998. I was wrong. Who could have known? :3
2010-01-30r300g: Independent blend enables only work on r500.Corbin Simpson
2010-01-30r300g: Don't handle SHADOW_AMBIENT.Corbin Simpson
Bisected so that only this commit has to be reverted if I'm wrong. ...Pfft, like I'm ever wrong. :3
2010-01-30r300g: Fix comment on SHADOW_AMBIENT.Corbin Simpson
2010-01-30gallium-docs: Fix missing PIPE_CAPs.Corbin Simpson
Hmm, need to cross-ref those TGSI things. My work is never done... :3
2010-01-30r300g: Dual-source blending isn't possible, period.Corbin Simpson
2010-01-30r300g: Add alpha render targets.Mathias Fröhlich
Signed-off-by: Corbin Simpson <MostAwesomeDude@gmail.com> Tested-by: Mathias Fröhlich <Mathias.Froehlich@gmx.net>
2010-01-30st/egl: eglBindTexImage should bind to an OpenGL ES texture.Chia-I Wu
The spec says that it only works with OpenGL ES.
2010-01-30egl: Rename Binding to CurrentContext in _EGLSurface.Chia-I Wu
A context can be bound to a surface just like it can be bound to a thread. CurrentContext is a more consistent name.
2010-01-30gallium: fix blend state csoRoland Scheidegger
if independent blend state was disabled, only the data from first rt was stored, however the comparison used the full state, hence there never was a match and always a new object was created. Fixes a huge performance drop with llvmpipe due to recompilation.
2010-01-29gallium: document pipe_context::get_query_result()Brian Paul
2010-01-29softpipe: support all TGSI fragment coord conventions (v4)Luca Barbieri
Changes in v4: - Rebase and modify for changes in previous patches Changes in v3: - Use positive caps instead of negative caps Changes in v2: - Now takes the fragment convention directly from the fragment shader Adds internal support for all fragment coord conventions to softpipe. This patch is not required for use with the current state trackers, but it allows softpipe to run any TGSI program and enhances performance.
2010-01-29tgsi: add caps for fragment coord conventions (v3)Luca Barbieri
Changes in v3: - Renumber caps to accomodate caps to add to master in the meantime - Document caps - Add unsupported caps to *_screen.c too Changes in v2: - Split for properties patch - Use positive caps instead of negative caps This adds 4 caps to indicate support of each of the fragment coord conventions. All drivers are also modifed to add the appropriate caps. Some drivers were incorrectly using non-Gallium-default conventions, and caps for them have them set so that they will behave correctly after the later state tracker patches. This drivers are softpipe/llvmpipe (uses integer rather than half integer) and pre-nv50 Nouveau (uses lower left rather than upper left). Other drivers might be broken. With this patchset, fixing them is only a matter of exposing the appropriate caps that match the behavior of the existing code. Drivers are encouraged to support all conventions themselves for better performance, and this feature is added to softpipe in a later patch.
2010-01-29tgsi: add properties for fragment coord conventions (v3)Luca Barbieri
Changes in v3: - Documented the new properties - Added comments for property values - Rebased to current master Changes in v2: - Caps are added in a separate, subsequent patch This adds two TGSI fragment program properties that indicate the fragment coord conventions. The properties behave as described in the extension spec for GL_ARB_fragment_coord_conventions, but the default origin in upper left instead of lower left as in OpenGL. The syntax is: PROPERTY FS_COORD_ORIGIN [UPPER_LEFT|LOWER_LEFT] PROPERTY FS_COORD_PIXEL_CENTER [HALF_INTEGER|INTEGER] The names have been chosen for consistency with the GS properties and the OpenGL extension spec. The defaults are of course the previously assumed conventions: UPPER_LEFT and HALF_INTEGER.
2010-01-28svga: Remove unnecessary headers.Vinson Lee
2010-01-28softpipe: Remove unnecessary header.Vinson Lee
2010-01-28llvmpipe: Remove unnecessary header.Vinson Lee
2010-01-28r300g: Clean up blend masks, change caps.Corbin Simpson
progs/tests/drawbuffers should work, except I can't test it. GG new shader parser. GG.
2010-01-28gallium-docs: Minor grammar, need to talk about dual-source blends.Corbin Simpson
2010-01-28gallium-docs: Clean up constantbuf info a bit.Corbin Simpson
Hmm, does this belong in context, next to set_constant_buffer? Maybe a paragraph in shaders might be useful.
2010-01-28gallium-docs: Add PIPE_CAP info.Corbin Simpson
2010-01-28st/xorg: Update to new libkms interface but be backwards compatibleJakob Bornecrantz
2010-01-28Merge commit 'origin/perrtblend'Roland Scheidegger
Conflicts: src/gallium/drivers/softpipe/sp_screen.c src/gallium/include/pipe/p_defines.h
2010-01-28gallium: remove PIPE_CAP_S3TC, and add PIPE_CAP_DUAL_SOURCE_BLENDRoland Scheidegger
there's no point in keeping deprecated PIPE_CAPS around since there's no stable interface (yet). Reuse the enum for PIPE_CAP_DUAL_SOURCE_BLEND. Drivers advertizing this will accept the pipe blendfactors with SRC1 in them and be able to do dual source blending (src color from pixel shader output 0, and blendfactor with SRC1 will come from output 1, only one render target may be bound when using any of these blend factors).
2010-01-28tgsi: Constants declared with ureg_DECL_constant() are one-dimensional.Michal Krol
This is to maintain backward compatibility with drivers that don't support arrays of constant buffers.
2010-01-28tgsi: Add ureg_property_gs_output_prim/max_vertices().Michal Krol
2010-01-28docs: Implement constant buffer CAPs.Michal Krol
2010-01-28softpipe: Report some sane values for constant buffer CAP queries.Michal Krol
2010-01-28gallium: Add CAPs for constant buffers.Michal Krol
2010-01-28gallium: Rename PIPE_MAX_CONSTANT to PIPE_MAX_CONSTANT_BUFFERS.Michal Krol
2010-01-28regress: Add vertex shaders tests for constant buffers.Michal Krol
2010-01-28gallium: Enable multiple constant buffers for vertex and geometry shaders.Michal Krol
2010-01-28regress: Add fragment shader test for one-dimensional constant buffers.Michal Krol
2010-01-28regress: Add two-dimension constant buffer test.Michal Krol
2010-01-28python: Link to ws2_32 on windows.Michal Krol
2010-01-28tgsi: Handle two-dimensional constants in text parser.Michal Krol
2010-01-28regress: Fix shader header.Michal Krol
2010-01-28gallium: Implement 2D constant buffers for fragment shader in softpipe.Michal Krol
2010-01-28tgsi: Handle 2-D declarations.Michal Krol
2010-01-28gallium: Add tgsi_declaration_dimension token.Michal Krol
This will allow us to declare two-dimensional constant buffers.
2010-01-28radeong: Slight improvement to buffer creation.Corbin Simpson
2010-01-28gallium-docs: Moar buffer info.Corbin Simpson
Oh look, that one question about map_buffer_range is answered.
2010-01-28gallium-docs: Start doc'ing screen buffers.Corbin Simpson
2010-01-28r300g: Fix bizarre half-flushes with immd mode.Corbin Simpson
2010-01-28r300g: Atomize framebuffers.Corbin Simpson
There might be some optimizations possible here...
2010-01-28egl: Migrate drivers to use _eglBindContext.Chia-I Wu
_eglMakeCurrent is a big hammer that is not easy to use. Migrate drivers to use _eglBindContext and un-export _eglMakeCurrent.
2010-01-28egl: eglMakeCurrent should accept an uninitialized display.Chia-I Wu
When no context or surface are given, the display is allowed to be uninitialized. Most drivers cannot handle an uninitialized display. But they are updated to at least throw a fatal message.
2010-01-28tgsi: Silence uninitialized variable warning.Vinson Lee
generated by cgit v1.2.3 (git 2.39.1) at 2024-07-04 01:56:29 +0000