summaryrefslogtreecommitdiffstats
path: root/src/mesa/main/context.c
Commit message (Collapse)AuthorAgeFilesLines
* mesa: Remove checks of Visual.rgbModeIan Romanick2010-03-031-2/+0
| | | | | | This must always be true now, so there is no reason to check it. Ever. Signed-off-by: Ian Romanick <[email protected]>
* mesa: Remove support for creating color-index visualsIan Romanick2010-03-031-10/+5
| | | | | | | | Remove the rgbMode and indexBits parameters from _mesa_create_visual and _mesa_initialize_visual. These values are now hardcoded to GL_TRUE and 0. Signed-off-by: Ian Romanick <[email protected]>
* Replace _mesa_malloc, _mesa_calloc and _mesa_free with plain libc versionsKristian Høgsberg2010-02-191-12/+12
|
* mesa: replace old MEMCPY macro with memcpyBrian Paul2010-02-191-1/+1
|
* 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
|
* mesa: Enable true refcounting for NullBufferObj.Michal Krol2010-02-091-0/+2
| | | | | | | | 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: Always do proper ref counting of shared state.José Fonseca2010-02-091-20/+4
|
* mesa: increase number of texture units to MAX_COMBINED_TEXTURE_IMAGE_UNITSBrian Paul2010-02-031-0/+3
| | | | | | | | | | | | | | | | | | | 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: Remove unnecessary headers.Vinson Lee2010-02-011-3/+0
|
* mesa: Remove unnecessary headers.Vinson Lee2010-01-311-4/+0
|
* mesa: do state validation in _mesa_valid_to_render()Brian Paul2010-01-291-0/+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)
* glapi: clean-up and simplify glapi_nop.c codeBrian Paul2010-01-221-8/+0
| | | | | | Removed _glapi_noop_enable_warnings() and _glapi_set_warning_func(). Just check the DEBUG env vars and call fprintf(stderr) with a warning message instead.
* mesa: call _mesa_compute_version() to set context's version infoBrian Paul2010-01-051-0/+5
|
* Merge branch 'mesa_7_7_branch'Brian Paul2009-12-111-4/+0
|\ | | | | | | | | | | Conflicts: src/gallium/state_trackers/xorg/xorg_xv.c src/mesa/drivers/dri/intel/intel_span.c
| * mesa: Move OES_read_format support from drivers into the core.Eric Anholt2009-12-091-4/+0
| | | | | | | | | | | | | | | | | | | | | | The assertion is that the correct read type to be using is the native type of the underlying read renderbuffer. For some fallback paths, this may be worse than GL_RGBA/GL_UNSIGNED_BYTE for reads today, but it gets all drivers the expected GL_BGRA/GL_UNSIGNED_BYTE for ARGB8888 or GL_BGR//GL_UNSIGNED_SHORT_5_6_5_REV for rgb565 with no work. This fixes the intel (and other) DRI drivers to report read formats that should hit blit PBO readpixels paths.
* | mesa: Update vertex texture code after gallium changes.Michal Krol2009-12-011-0/+1
|/
* Merge branch 'outputswritten64'Ian Romanick2009-11-171-3/+5
| | | | | | | | | | | | | | | | | | | | | | | | Add a GLbitfield64 type and several macros to operate on 64-bit fields. The OutputsWritten field of gl_program is changed to use that type. This results in a fair amount of fallout in drivers that use programs. No changes are strictly necessary at this point as all bits used are below the 32-bit boundary. Fairly soon several bits will be added for clip distances written by a vertex shader. This will cause several bits used for varyings to be pushed above the 32-bit boundary. This will affect any drivers that support GLSL. At this point, only the i965 driver has been modified to support this eventuality. I did this as a "squash" merge. There were several places through the outputswritten64 branch where things were broken. I foresee this causing difficulties later for bisecting. The history is still available in the branch. Conflicts: src/mesa/drivers/dri/i965/brw_wm.h
* mesa/main: Make FEATURE_texture_s3tc follow feature conventions.Chia-I Wu2009-10-291-3/+1
| | | | Signed-off-by: Chia-I Wu <[email protected]>
* mesa/main: Make FEATURE_texture_fxt1 follow feature conventions.Chia-I Wu2009-10-291-3/+0
| | | | | | Also remove the unused initialization and GLchan fetch functions. Signed-off-by: Chia-I Wu <[email protected]>
* glapi: Always build libglapi.a.Chia-I Wu2009-10-231-1/+0
| | | | | | | | This is made possible by making glapioffsets.h and glapidispatch.h internal headers of glapi. They should only be included indirectly through dispatch.h by mesa. Signed-off-by: Chia-I Wu <[email protected]>
* mesa: Enable remap table in core.Chia-I Wu2009-10-231-0/+3
| | | | | | | | | | | | | This enables the remap table in core. driInitExtensions is adapted to use the remap table. All uses of extension_helper.h are replaced by remap_helper.h. The chicken-egg problem of the DRI drivers is also solved. It is now also possible to pass NULL extensions to driInitExtensions. It will cause driInitExtensions to map all known functions. This functionality is used by software drivers and EGL_i915. Signed-off-by: Chia-I Wu <[email protected]>
* Merge branch 'mesa_7_6_branch'Brian Paul2009-10-221-8/+29
|\
| * mesa: code refactoring- new _mesa_finish(), _mesa_flush()Brian Paul2009-10-221-8/+29
| |
* | mesa: added VERBOSE_SWAPBUFFERSBrian Paul2009-10-141-0/+2
| |
* | mesa: free display list state after freeing shared stateBrian Paul2009-10-081-1/+3
| | | | | | | | Fixes bug 24402.
* | mesa: added _mesa_free_display_list_data()Brian Paul2009-10-071-0/+1
| |
* | Merge branch 'mesa_7_6_branch'Brian Paul2009-10-051-0/+1
|\| | | | | | | | | | | Conflicts: src/gallium/auxiliary/util/u_cpu_detect.c
| * mesa: add missing return when out of memoryBrian Paul2009-10-011-0/+1
| |
* | mesa/main: Make FEATURE_dlist follow feature conventions.Chia-I Wu2009-09-301-5/+3
| | | | | | | | | | As shown in mfeatures.h, this allows users of dlist.h to work without knowing if the feature is available.
* | mesa/main: Make FEATURE_evaluators follow feature conventions.Chia-I Wu2009-09-301-6/+0
| | | | | | | | | | As shown in mfeatures.h, this allows users of eval.h to work without knowing if the feature is available.
* | mesa/main: New feature FEATURE_queryobj.Chia-I Wu2009-09-301-8/+2
| | | | | | | | | | It merges FEATURE_ARB_occlusion_query and FEATURE_EXT_timer_query, and follows the feature conventions.
* | mesa/main: Make FEATURE_feedback follow feature conventions.Chia-I Wu2009-09-301-6/+0
| | | | | | | | | | As shown in mfeatures.h, this allows users of feedback.h to work without knowing if the feature is available.
* | mesa/main: New feature FEATURE_rastpos.Chia-I Wu2009-09-301-4/+0
| | | | | | | | | | It is separated from FEATURE_drawpix and made to follow the feature conventions.
* | mesa/main: Make FEATURE_histogram follow feature conventions.Chia-I Wu2009-09-301-4/+0
| | | | | | | | | | As shown in mfeatures.h, this allows users of histogram.h to work without knowing if the feature is available.
* | mesa/main: Make FEATURE_attrib_stack follow feature conventions.Chia-I Wu2009-09-301-6/+0
| | | | | | | | | | As shown in mfeatures.h, this allows users of attrib.h to work without knowing if the feature is available.
* | mesa/main: Make FEATURE_accum follow feature conventions.Chia-I Wu2009-09-301-4/+0
| | | | | | | | | | As shown in mfeatures.h, this allows users of accum.h to work without knowing if the feature is available.
* | mesa/main: Make FEATURE_colortable follow feature conventions.Chia-I Wu2009-09-241-6/+0
| | | | | | | | | | As shown in mfeatures.h, this allows users of colortab.h to work without knowing if the feature is available.
* | Revert "mesa: move _mesa_meta_init/free() calls to core Mesa"Brian Paul2009-09-201-5/+0
| | | | | | | | | | | | This reverts commit 651cffd626a82d9bf539437ca4bdf8ea4b396fab. The commit inadvertantly introduced a new gallium dependency on the meta code.
* | mesa: move _mesa_meta_init/free() calls to core MesaBrian Paul2009-09-191-0/+5
|/
* ARB sync: Add support for GL_ARB_sync to swrastIan Romanick2009-09-031-0/+12
| | | | | This isn't quite right yet. The delete behavior and the context clean-up needs some work.
* ARB prog: Change handling of program parameter limitsIan Romanick2009-08-261-10/+12
| | | | | | | | | | | | | | | | | Several changes are made to program parameter limits. Several of the non-NATIVE limits are set higher. All of the NATIVE limits are set to zero in the core Mesa code. Each driver must set the actual value in its context creation routine. If the NATIVE value remains zero, this indicates that hardware shaders may not be supported. Each of the preceeding changes matches the bahavior of Apple's shader assembler, so it seems safe. Finally, we limit the value of MaxEnvParams to be no greater than MaxNativeAttribs. At least one case has been found where an application does the wrong thing if MaxNativeAttribs < MaxEnvParams. See also bugzilla #23490.
* mesa: validate shader before drawing (for debugging, disabled)Brian Paul2009-08-251-0/+10
|
* mesa: append uniform values to the log file the first time we use a shaderBrian Paul2009-08-141-0/+27
| | | | | This info is essential to using/debugging a shader outside of its normal application.
* mesa: new _mesa_valid_to_render() functionBrian Paul2009-08-141-0/+42
| | | | | Tests if the current shader/program is valid and that the framebuffer is complete. To be called by glBegin, glDrawArrays, etc.
* Merge branch 'arb_vertex_array_object'Brian Paul2009-06-261-0/+1
|\
| * mesa: move vertex array objects from shared state to per-contextBrian Paul2009-06-191-0/+1
| | | | | | | | | | The ARB version requires VAOs to be per-context while the Apple extension was ambiguous.
* | Merge branch 'mesa_7_5_branch'Brian Paul2009-06-241-12/+29
|\ \ | |/ |/| | | | | | | | | | | | | | | | | | | | | Conflicts: src/mesa/drivers/dri/i915/i915_tex_layout.c src/mesa/drivers/dri/i965/brw_wm_glsl.c src/mesa/drivers/dri/intel/intel_buffer_objects.c src/mesa/drivers/dri/intel/intel_pixel_bitmap.c src/mesa/drivers/dri/intel/intel_pixel_draw.c src/mesa/main/enums.c src/mesa/main/texstate.c src/mesa/vbo/vbo_exec_array.c
| * mesa: rework viewport/scissor initialization codeBrian Paul2009-06-171-12/+29
| | | | | | | | | | | | | | | | | | | | The first time a context is bound to a drawable, the viewport and scissor bounds are initialized to the buffer's size. This is actually a bit tricky. A new _mesa_check_init_viewport() function is called in several places to check if the viewport has been initialized. We also use a new ctx->ViewportInitialized flag instead of the overloaded ctx->FirstTimeCurrent flag.
* | Merge branch 'ext-provoking-vertex'Brian Paul2009-06-191-0/+3
|\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: docs/relnotes-7.6.html progs/tests/Makefile src/gallium/drivers/softpipe/sp_prim_vbuf.c src/glx/x11/indirect.c src/mesa/glapi/Makefile src/mesa/glapi/dispatch.h src/mesa/glapi/glapioffsets.h src/mesa/glapi/glapitable.h src/mesa/glapi/glapitemp.h src/mesa/glapi/glprocs.h src/mesa/main/dlist.c src/mesa/main/enums.c src/mesa/sparc/glapi_sparc.S src/mesa/x86-64/glapi_x86-64.S src/mesa/x86/glapi_x86.S
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-18 12:03:30 +0000