summaryrefslogtreecommitdiffstats
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
* gallium: also save/restore stencil_ref in cso_save/restore_depth_stencil_alphaRoland Scheidegger2010-02-112-20/+8
| | | | makes life of state trackers easier
* svga: adapt to stencil ref changesRoland Scheidegger2010-02-103-6/+42
| | | | also add some disabled code to handle blendcolor?
* llvmpipe: adapt to stencil ref changesRoland Scheidegger2010-02-104-2/+28
| | | | since the driver doesn't actually handle stencil yet the code won't do much.
* identity: adapt to stencil ref changesRoland Scheidegger2010-02-101-0/+12
|
* fo: adapt to stencil ref changesRoland Scheidegger2010-02-103-6/+24
|
* st/mesa: more fixes for stencil ref change.Roland Scheidegger2010-02-102-2/+20
| | | | | compiles. Might need to do something to make it possible to save/restore stencil ref.
* trace: adapt to stencil ref changesRoland Scheidegger2010-02-103-1/+37
|
* softpipe: adapt to stencil ref changesRoland Scheidegger2010-02-106-6/+20
|
* gallium: adapt state trackers to stencil ref changeRoland Scheidegger2010-02-103-13/+18
|
* docs: fix up documentation for stencil ref value changesRoland Scheidegger2010-02-092-8/+12
| | | | Also fix and clarify depth/stencil/alpha documentation a bit.
* gallium: make valuemask/writemask in pipe_stencil_state bitfield membersRoland Scheidegger2010-02-091-2/+2
| | | | | More consistent with other state data, might allow some compilers to pack the struct better (doesn't matter for gcc).
* gallium: don't put stencil ref value in pipe_depth_stencil_alpha_stateRoland Scheidegger2010-02-096-50/+60
| | | | | | | | This will make driver's life a bit harder, however it makes sense that stencil reference value is not part of the pipe_depth_stencil_alpha_state, because it often (there are some algorithms which require this) changes more frequently than the rest of the dsa state. This is also encouraged by some graphic APIs. Treat it similar to pipe_blend_color.
* Merge branch 'gallium-nopointsizeminmax'Roland Scheidegger2010-02-0928-104/+1381
|\ | | | | | | | | | | | | Conflicts: src/gallium/drivers/nv10/nv10_state.c src/gallium/drivers/nv20/nv20_state.c src/gallium/drivers/nv50/nv50_program.c
| * st/mesa: fix wrong initialization of MaxPointSizeRoland Scheidegger2010-02-081-0/+4
| |
| * gallium: add point_quad_rasterization bit to rasterizer stateRoland Scheidegger2010-02-0410-6/+22
| | | | | | | | | | This determines if points should be rasterized according to GL point rules or as normal quads (GL point sprites / d3d points / d3d point sprites).
| * gallium: add point size clamp to implementation limits in vertex shaderRoland Scheidegger2010-02-045-1/+108
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The point size min/max registers (unused by mesa state tracker) were removed since most hardware couldn't do much with them. However, we don't want to have to rely on hw to do point size clamping correctly to implementation dependent limits, hence have to do that in the vertex shader. This should also solve a potential problem with (non-AA) points smaller than 1.0 which according to OGL still have size 1.0. Note that OGL point rendering is odd, in particular point sprites are rasterized differently to points. Some hardware might support those different modes, but in any case the different clamping values used for smooth/multisampled/sprite enabled points might help a bit for hw which rasterizes points the same as point sprites. Also tweak mesa's ff to vertex shader translation so don't have to clamp twice in case of point attenuation.
| * docs: clean up TGSI_SEMANTIC_PSIZE descriptionRoland Scheidegger2010-02-031-4/+2
| | | | | | | | there was some confusion between point size state and point size output.
| * docs: fix point sprite documentationRoland Scheidegger2010-02-031-9/+10
| |
| * gallium: clean up point sprite rasterizer stateRoland Scheidegger2010-02-0318-62/+64
| | | | | | | | | | | | | | | | | | | | Don't need sprite coord origin per coord. Also, don't need separate sprite enable bit - if all coords have it diabled, then there are no point sprites (technically, there's a distinction in pre-GL3, but it only differs in having more leniency in clamping to max size, something the state tracker would need to handle and the hardware won't bother anyway). Also, use packed field for the per-coord enables. All in all, should save 3 dwords in rasterizer state (from 10 down to 7).
| * gallium: remove point_size_min and point_size_max from rasterizer stateRoland Scheidegger2010-01-1211-35/+11
| | | | | | | | | | | | | | The state tracker is responsible for clamping to any graphics API enforced size min/max limits for both the static point_size setting as well as per vertex point size (in the vertex shader). Note that mesa state tracker didn't actually use these values.
* | gallium: Adding the %.s rule to generate asm codeChris Li2010-02-091-0/+3
| | | | | | | | Signed-off-by: José Fonseca <[email protected]>
* | gallium: Using the proper pattern rules for Makefile template.Chris Li2010-02-091-3/+3
| | | | | | | | | | | | The .o.c rule is consider obsolete. Signed-off-by: José Fonseca <[email protected]>
* | llvmpipe: Make llvm unit test depend on libllvmpipe.aChris Li2010-02-091-3/+2
| | | | | | | | Signed-off-by: José Fonseca <[email protected]>
* | vmware/core: Support drm interface version 1.0.0Jakob Bornecrantz2010-02-061-1/+1
| |
* | vmware/core: Use correct flags in scanout codeJakob Bornecrantz2010-02-061-4/+4
| |
* | vmware/core: Handle new scanout fieldJakob Bornecrantz2010-02-064-4/+35
| |
* | vmware/core: Update header to latest versionJakob Bornecrantz2010-02-061-3/+9
| |
* | vmware/core: Remove old ioctl structs not usedJakob Bornecrantz2010-02-061-43/+0
| | | | | | | | Leftover that was never used in this driver
* | llvmpipe: Remove reference to prefilter field.Michal Krol2010-02-091-1/+0
| |
* | glx: Fix TOP setting in src/glx MakefileKristian Høgsberg2010-02-091-1/+1
| | | | | | | | Argh, forgot to commit this fix before pushing.
* | Retire miniglx and move the actual glx code up to src/glxKristian Høgsberg2010-02-0962-4356/+104
| |
* | egl_dri2: Fix initialization with EGL_DEFAULT_DISPLAYKristian Høgsberg2010-02-091-6/+6
| |
* | fix bug in perspective corrected interpolants for linesBrian Paul2010-02-091-2/+1
| |
* | st/mesa: remove special-case cyl-wrap codeBrian Paul2010-02-091-9/+1
| | | | | | | | Cylinder wrap mode works with perspective interpolation now.
* | softpipe: Properly implement cylindrical wrapping.Michal Krol2010-02-091-31/+148
| |
* | Revert "softpipe: Implement cylindrical wrapping for linear interpolator."Michal Krol2010-02-091-35/+11
| | | | | | | | This reverts commit 444cd62ca33a45bd39e8408979a0a01c246c6381.
* | st/mesa: check for PROG_PARAM_BIT_CYL_WRAP flagBrian Paul2010-02-092-5/+22
| |
* | mesa: add back-door support for cylindrical texture wrap modeBrian Paul2010-02-092-0/+13
| | | | | | | | | | | | | | | | | | If the texture priority field is 0.125 set the PROG_PARAM_BIT_CYL_WRAP flag. The gallium state tracker will look for this flag. This feature is only for testing purposes and may be remove at some point. But if it's useful we could write a GL/Mesa extension to expose it properly.
* | gallium: Remove prefilter member from pipe_sampler_state struct.Michal Krol2010-02-098-9/+0
| |
* | docs: Document TGSI Declaration token.Michal Krol2010-02-091-0/+28
| |
* | softpipe: Implement cylindrical wrapping for linear interpolator.Michal Krol2010-02-091-11/+35
| |
* | tgsi: Gather cylindrical wrap info in tgsi_shader_info struct.Michal Krol2010-02-092-0/+2
| |
* | tgsi: Add ureg_DECL_fs_input_cyl().Michal Krol2010-02-092-52/+94
| | | | | | | | Allows one to declare fragment shader inputs with cylindrical wrap info.
* | gallium: Add cylindrical wrap info to TGSI declaration.Michal Krol2010-02-094-3/+28
| |
* | tgsi: Remove tgsi_dump_c.[ch].Michal Krol2010-02-093-512/+0
| | | | | | | | Little utility after development stabilisation, use tgsi_dump instead.
* | mesa: Enable true refcounting for NullBufferObj.Michal Krol2010-02-098-10/+48
| | | | | | | | | | | | | | | | This object can be shared with another context, so we cannot just delete it when the owning context is being destroyed. Ensuring that buffer objects are properly refcounted guarantees NullBufferObj is destroyed when all references to it are removed.
* | mesa: Protect buffer objects reference counting with a mutex.Michal Krol2010-02-092-4/+7
| |
* | mesa: Ensure object refcount is null when destroying the buffer.José Fonseca2010-02-091-0/+2
| | | | | | | | | | | | | | | | Lets see if this is not too pedantic. Obj pointers are never exposed to GL apps so it should be possible to get this right. Furthermore apps with GL widgets and test suits create and destroy many contexts and objects, so bad reference counting is not really an option.
* | mesa: Fix null buffer object reference counting.José Fonseca2010-02-092-6/+19
| | | | | | | | | | | | | | | | Always use _mesa_reference_buffer_object, and never call ctx->Driver.DeleteBuffer() directly to prevent dangling pointers to the null buffer object. This fixes crash/assertions in sharedtex_mt and Autodesk Mudbox.
* | mesa: Always do proper ref counting of shared state.José Fonseca2010-02-093-23/+34
| |
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-22 10:59:26 +0000