summaryrefslogtreecommitdiffstats
path: root/src/mesa/main
Commit message (Collapse)AuthorAgeFilesLines
* Remove _mesa_strcpy in favor of plain strcpy.Kenneth Graunke2010-02-192-12/+2
|
* Remove _mesa_strncat in favor of plain strncat.Kenneth Graunke2010-02-192-10/+0
|
* Remove _mesa_strstr in favor of plain strstr.Kenneth Graunke2010-02-193-14/+4
|
* mesa: Lock mutex around _mesa_HashLookup linked list chase.Brian Paul2010-02-162-3/+6
| | | | | | | | | Remove const qualifier from _mesa_HashLookup() table parameter to avoid LOCK/UNLOCK warnings in the function body. Signed-off-by: Brian Paul <[email protected]> (cherry picked from commit 3094adb3caeb90124359db2356df3bf8ee94800a)
* mesa: Test for failed malloc in _mesa_HashInsert.Brian Paul2010-02-161-4/+6
| | | | | | Signed-off-by: Brian Paul <[email protected]> (cherry picked from commit 7c7247ddbf6e3f7f93e44c1cb52490044f1a2215)
* mesa: Don't pass paramter to __builtin_clz which would hve undefined result.Pauli Nieminen2010-02-141-5/+11
| | | | | | | | | __builtin_clz with parameter 0 has undefined value. When using -O3 optimizing this would result to too large next power of two value. Fix is to check if passed value is 1 and modify formula for that case.
* mesa: Fix compiler warningsKarl Schultz2010-02-134-17/+17
| | | | | Add explicit casts, fix constant types, fix variable types. Fixes about 340 warnings in MSFT Visual Studio.
* mesa: enable GL_ARB_fragment_coord_conventions for sw driversBrian Paul2010-02-131-2/+2
| | | | | This extension is now implemented in the GLSL compiler so it can be enabled by other drivers where applicable.
* mesa: Export GL_EXT_texture_cube_map.José Fonseca2010-02-131-0/+1
| | | | Still used by some applications.
* mesa: s/abort/sys.exit/Vinson Lee2010-02-131-1/+2
| | | | Python does not have the function abort.
* mesa: Remove unnecessary header.Vinson Lee2010-02-122-2/+0
|
* main: Fix compiler warning. No need to convert/store depthScale as GLfloat ↵Karl Schultz2010-02-111-2/+2
| | | | | | just to convert it back to GLuint to call unpack_depth_span. Also removes a difference between the 24/8 and 8/24 texstore routines.
* mesa: additional constant/limit assertionsBrian Paul2010-02-111-0/+5
|
* mesa: move all limit/constant assertions into check_context_limits()Brian Paul2010-02-091-30/+30
|
* Merge branch 'gallium-nopointsizeminmax'Roland Scheidegger2010-02-091-1/+1
|\ | | | | | | | | | | | | Conflicts: src/gallium/drivers/nv10/nv10_state.c src/gallium/drivers/nv20/nv20_state.c src/gallium/drivers/nv50/nv50_program.c
| * gallium: add point size clamp to implementation limits in vertex shaderRoland Scheidegger2010-02-041-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | Retire miniglx and move the actual glx code up to src/glxKristian Høgsberg2010-02-091-1/+1
| |
* | mesa: add back-door support for cylindrical texture wrap modeBrian Paul2010-02-091-0/+12
| | | | | | | | | | | | | | | | | | 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.
* | mesa: Enable true refcounting for NullBufferObj.Michal Krol2010-02-096-8/+26
| | | | | | | | | | | | | | | | 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: Fix null buffer object reference counting.José Fonseca2010-02-091-6/+8
| | | | | | | | | | | | | | | | 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
| |
* | mesa: Fix mesa_next_pow_two to return same value if parameter is pow2.Pauli Nieminen2010-02-071-3/+5
| | | | | | | | | | Without subtracting one pow2 value would be rounded up to next pow2 which is not correct behaviour for the function.
* | mesa/main: Add function to find next higher power of two.Pauli Nieminen2010-02-061-0/+46
| | | | | | | | | | | | | | | | | | With gcc implementation uses __builtin_clr which counts number of leading zeros. Fallback implementation uses bit manipulation. First it duplicates the highest bit to all lower bits and then adds one to get the power of two number.
* | mesa: change ctx->Driver.ProgramStringNotify() to return GLbooleanBrian Paul2010-02-042-5/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | GL_TRUE indicates that the driver accepts the program. GL_FALSE indicates the program can't be compiled/translated by the driver for some reason (too many resources used, etc). Propogate this result up to the GL API: set GL_INVALID_OPERATION error if glProgramString() was called. Set shader program link status to GL_FALSE if glLinkProgram() was called. At this point, drivers still don't do any program checking and always return GL_TRUE.
* | mesa: increase number of texture units to MAX_COMBINED_TEXTURE_IMAGE_UNITSBrian Paul2010-02-034-13/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We were misinterpretting GL_MAX_COMBINED_TEXTURE_IMAGE_UNITS previously. It's the number of texture units for which we need to keep state; not just the total number of texture units addressable by the vertex shader plus fragment shader. Since sw Mesa independently supports 16 texture units in vertex shaders and 16 texture units in fragment shaders, the max combined units is 32. Note that the docs for glActiveTexture() indicate the max legal unit is MAX(GL_MAX_COMBINED_TEXTURE_IMAGE_UNITS, MAX_TEXTURE_COORDS) - 1. A new piglit test (texunits.c) tests the various texture unit limits. I'm pretty sure I've got this all right now, but additional reviews are welcome...
* | mesa: re-dimension RasterTexCoords and CoordReplaceBrian Paul2010-02-031-2/+2
| | | | | | | | These are limited to the number of texture coordinate units.
* | mesa: added texcoord unit assertionBrian Paul2010-02-031-0/+2
| |
* | mesa: use Elements() instead of MAX_TEXTURE_COORD_UNITSBrian Paul2010-02-031-1/+1
| |
* | mesa: added tex unit assert, use Elements() macroBrian Paul2010-02-031-1/+2
| |
* | mesa: check for invalid texture coord unit in glGet queriesBrian Paul2010-02-032-56/+147
| |
* | mesa: add error check for querying invalid texture matrixBrian Paul2010-02-032-5/+41
| |
* | mesa: use Elements() as limit in loops over texture/program matrix stacksBrian Paul2010-02-031-4/+4
| |
* | mesa: add out of bounds assertions for accessing texture matrix stackBrian Paul2010-02-031-0/+2
| |
* | mesa: Factor out the fb initialization details from _mesa_new_framebuffer.Francisco Jerez2010-02-032-13/+34
| | | | | | | | | | | | | | | | | | | | | | This should make things easier for drivers wanting to work with a "subclass" of gl_framebuffer. The complementary "_mesa_initialize_framebuffer" function is now called "_mesa_initialize_window_framebuffer" for the sake of symmetry. Signed-off-by: Brian Paul <[email protected]>
* | mesa: Add a BITSET_FFS function.Francisco Jerez2010-02-021-1/+24
| | | | | | | | | | | | | | It will be useful for the nouveau DRI driver and IMHO there's no reason to keep it private. Signed-off-by: Brian Paul <[email protected]>
* | mesa: Remove unnecessary headers.Vinson Lee2010-02-013-7/+0
| |
* | mesa: Remove unnecessary headers.Vinson Lee2010-01-314-10/+0
| |
* | Merge commit 'lb2/arb_fragment_coord_conventions'Keith Whitwell2010-01-291-1/+2
|\ \
| * | mesa: don't expose GL_ARB_fragment_coord_conventions until the GLSL part is doneLuca Barbieri2010-01-291-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | Exposing it was incorrect, as the GLSL part of the extension is missing. We still keep the ARB_fragment_coord_conventions field, so that the ARBfp parser can know whether to accept or reject the keywords.
* | | mesa: do state validation in _mesa_valid_to_render()Brian Paul2010-01-292-9/+4
|/ / | | | | | | | | | | | | | | | | ...rather than checking/validating before all the calls to _mesa_valid_to_render() and valid_to_render(). The next patch will actually fix some bugs... (cherry picked from commit 23eda89ec89e2bd5bc26077bd56e8d6b5d4040d4)
* | mesa: fix double->float assignment warningsBrian Paul2010-01-271-3/+3
| | | | | | | | Reported by Karl Schultz.
* | mesa: fix int/uint comparison warningsBrian Paul2010-01-272-7/+7
| | | | | | | | Reported by Karl Schultz.
* | mesa: more info in glActiveTexture error msgBrian Paul2010-01-271-1/+2
| |
* | Merge branch 'mesa_7_7_branch'Brian Paul2010-01-262-14/+19
|\ \ | | | | | | | | | Merging was easier than cherry picking in this instance.
| * | mesa: Don't bind DRAW/READ_FRAMEBUFFER separately without FBO blit supportErik Wien2010-01-261-8/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If GL_EXT_framebuffer_blit was not supported _mesa_DeleteFramebuffersEXT would raise an error when deleting the currently bound framebuffer. This because it tried to bind the default DRAW- and READ_FRAMEBUFFER separately. This patch binds the default FRAMEBUFFER instead in that case. Encountered in the fbo/fbo-copyteximage piglit test on R600. Patch cleaned up a bit by Brian Paul.
| * | mesa: remove redundant _MaxElement computationBrian Paul2010-01-261-6/+0
| | | | | | | | | | | | | | | | | | | | | | | | Eric added some new code to check if offset < obj_size before computing _MaxElement but my original code was still present afterward and it clobbered the _MaxElement value. Not sure if this came from a bad merge or what.
* | | Merge branch 'mesa_7_7_branch'Brian Paul2010-01-251-3/+3
|\| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: src/mesa/drivers/dri/intel/intel_screen.c src/mesa/drivers/dri/intel/intel_swapbuffers.c src/mesa/drivers/dri/r300/r300_emit.c src/mesa/drivers/dri/r300/r300_ioctl.c src/mesa/drivers/dri/r300/r300_tex.c src/mesa/drivers/dri/r300/r300_texstate.c
| * | mesa: move _mesa_debug() call earlier in _mesa_ScissorBrian Paul2010-01-241-3/+3
| | | | | | | | | | | | Part of a patch from Xavier Chantry <[email protected]>
* | | Merge branch 'arb_half_float_vertex'Dave Airlie2010-01-234-2228/+2255
|\ \ \
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-22 22:29:39 +0000