summaryrefslogtreecommitdiffstats
path: root/src/mesa
Commit message (Collapse)AuthorAgeFilesLines
* r300: further cleanupMaciej Cencora2009-05-167-85/+82
| | | | | | | - move extensions init into seperate function - move options handling into seperate function - create new structure to hold options values - use context->options.hw_tcl_enabled field instead of global hw_tcl_on and future_hw_tcl_on variables
* r300: don't send now forbidden register to kernel when with memory managerJerome Glisse2009-05-143-16/+67
|
* R1xx/r2xx: Don't use an alpha texture format for GLX_TEXTURE_FORMAT_RGB_EXTAlex Deucher2009-05-132-2/+8
| | | | | | | | In r*00SetTexBuffer2(), if the passed in text glx_texture_format is GLX_TEXTURE_FORMAT_RGB_EXT, then we should use an RGB-only texture format, even if the DRI buffer has four channels. https://bugs.freedesktop.org/show_bug.cgi?id=21609
* radeon: Don't crash generating mipmaps when pixels=NULLOwen W. Taylor2009-05-131-9/+8
| | | | | | | | | When a NULL value of pixels is passed to TexImage2D and SGIS_generate_mipmap is enabled, don't try to generate the mipmap tree: we don't have data yet for the texture and will crash. https://bugs.freedesktop.org/show_bug.cgi?id=21648
* Don't use an alpha texture format for GLX_TEXTURE_FORMAT_RGB_EXTOwen W. Taylor2009-05-131-1/+4
| | | | | | | | In r300SetTexBuffer2(), if the passed in text glx_texture_format is GLX_TEXTURE_FORMAT_RGB_EXT, then we should use an RGB-only texture format, even if the DRI buffer has four channels. https://bugs.freedesktop.org/show_bug.cgi?id=21609
* Call _mesa_update_stencil() before accessing ctx->Stencil._EnabledOwen W. Taylor2009-05-131-0/+2
| | | | | | | | ctx->Stencil._Enabled is derived state and not immediately updated when the stencil parameters are changed; we need to make sure that it is up-to-date before accessing it. https://bugs.freedesktop.org/show_bug.cgi?id=21608
* Remove subpixel offset from viewportOwen W. Taylor2009-05-131-10/+4
| | | | | | | | Remove an eigth-pixel offset of the viewport inherited from R100 code. This seems not to be necessary and causes blurring when sampling textures 1:1. https://bugs.freedesktop.org/show_bug.cgi?id=20340
* radeon: glReadBuffer set _NEW_BUFFERS, not _NEW_PIXELJerome Glisse2009-05-123-4/+4
| | | | | This was broken with last merge see 62043b27575c378c027251316421e4699f461108 for explanations
* r300/r500: make sure we detect constant buffer changesJerome Glisse2009-05-121-1/+1
| | | | | This was broken with last merge see f48473e42511f8d37a239a07f791bc0a87209e5b for explanations.
* radeon: avoid segfault in radeon_update_renderbuffers() if using DRI1Tormod Volden2009-05-121-3/+4
| | | | | | Basically the same as 43d9020ff1e975e7f4f9480d9ef24f0b9fb2141f for intel. Bug 21688. Signed-off-by: Tormod Volden <[email protected]>
* radeon: add support for new dri2 interfaces & fix single buffer renderingJoel Bosveld2009-05-103-16/+154
|
* Merge commit 'origin/master' into radeon-rewriteJerome Glisse2009-05-10108-1151/+2937
|\ | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: src/mesa/drivers/dri/r200/r200_state.c src/mesa/drivers/dri/r300/r300_context.h src/mesa/drivers/dri/r300/r300_fragprog.c src/mesa/drivers/dri/r300/r300_state.c src/mesa/drivers/dri/r300/r300_texmem.c src/mesa/drivers/dri/r300/r300_texstate.c src/mesa/drivers/dri/r300/r500_fragprog.c src/mesa/drivers/dri/radeon/radeon_screen.c src/mesa/drivers/dri/radeon/radeon_state.c
| * i965: improve debug loggingRobert Ellison2009-05-083-14/+86
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Looking for memory leaks that were causing crashes in my environment in a situation where valgrind would not work, I ended up improving the i965 debug traces so I could better see where the memory was being allocated and where it was going, in the regions and miptrees code, and in the state caches. These traces were specific enough that external scripts could determine what elements were not being released, and where the memory leaks were. I also ended up creating my own backtrace code in intel_regions.c, to determine exactly where regions were being allocated and for what, since valgrind wasn't working. Because it was useful, I left it in, but disabled and compiled out. It can be activated by changing a flag at the top of the file.
| * i965: fix memory leak in context/renderbuffer region managementRobert Ellison2009-05-081-4/+60
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | A temporary change to the intelMakeCurrent() function to make it work with frame buffer objects causes the static regions associated with the context (the front_region, back_region, and depth_region) to take on an additional reference, with no corresponding release. This causes a memory leak if a program repeatedly creates and destroys contexts. The fix is the corresponding hack, to unreference these regions when the context is deleted, but only if the framebuffer objects are still present and the same regions are still referenced within. Both sets of code have comment blocks referring to each other.
| * i965: fix segfault on low memory conditionsRobert Ellison2009-05-081-0/+7
| | | | | | | | | | | | | | When out of memory (in at least one case, triggered by a longrunning memory leak), this code will segfault and crash. By checking for the out-of-memory condition, the system can continue, and will report the out-of-memory error later, a much preferable outcome.
| * mesa: Fixed a texture memory leakRobert Ellison2009-05-081-0/+3
| | | | | | | | | | | | | | | | | | | | | | | | The current texture for any particular texture unit is given an additional reference in update_texture_state(); but if the context is closed before that texture can be released (which is quite frequent in normal use, unless a program unbinds and deletes the texture and renders without it to force a call to update_texture_state(), the memory is lost. This affects general Mesa; but the i965 is particularly affected because it allocates a considerable amount of additional memory for each allocated texture.
| * intel: Add a metaops version of glGenerateMipmapEXT/SGIS_generate_mipmaps.Eric Anholt2009-05-0810-76/+303
| | | | | | | | | | | | | | In addition to being HW accelerated, it avoids the incorrect (black) rendering of the mipmaps that SW was doing in fbo-generatemipmap. Improves the performance of the mipmap generation and drawing in fbo-generatemipmap by 30%.
| * intel: Put the constant texcoords used in metaops into a vbo.Eric Anholt2009-05-085-40/+102
| | | | | | | | | | | | | | Make this be its own function for setup/teardown of the binding of these texcoords. No performance difference in the engine demo (I just felt dirty not using a VBO for this), and I think it should be more resilient to interference from current GL state.
| * i965: const qualifiersBrian Paul2009-05-081-2/+2
| |
| * mesa: raise MAX_VARYING (number of shader varying vars) to 16Brian Paul2009-05-081-1/+1
| | | | | | | | 16 is the limit for now because of various 32-bit bitfields.
| * mesa: assertions to check for too many vertex outputs or fragment inputsBrian Paul2009-05-081-0/+4
| |
| * glsl: check number of varying variables against the limitBrian Paul2009-05-081-4/+9
| | | | | | | | Link fails if too many varying vars.
| * mesa: issue warning for out of bounds array indexesBrian Paul2009-05-081-0/+2
| |
| * i965: don't use GRF regs 126,127 for WM programsBrian Paul2009-05-082-5/+28
| | | | | | | | | | | | | | They seem to be used for something else and using them for shader temps seems to lead to GPU lock-ups. Call _mesa_warning() when we run out of temps. Also, clean up some debug code.
| * glsl: set vertex/fragment program Ids to aid with debuggingBrian Paul2009-05-081-0/+4
| |
| * mesa: more shader debug code (disabled)Brian Paul2009-05-081-0/+4
| |
| * mesa/st: keep surface_copy arguments positiveKeith Whitwell2009-05-082-3/+68
| | | | | | | | | | | | | | The src/dest x,y, and w,h arguments of the pipe->surface_copy function are unsigned and the drivers aren't expecting negative (or extremly-large unsigned) values as inputs. Trim the requests at the state-tracker level before passing down.
| * mesa/st: remove redundant call to st_finish in CopyTexSubImageKeith Whitwell2009-05-081-3/+0
| | | | | | | | | | Rendering should already have been flushed, any synchronization will be done by the driver or memory manager.
| * mesa/st: cope with non-ibo index data in st_draw_feedback.cKeith Whitwell2009-05-081-8/+15
| | | | | | | | | | | | Previously only non-indexed or indicies-in-a-vbo cases were handled in this code. This change adds the missing regular indices-in-memory case.
| * mesa: Make _mesa_share_state thread safe.José Fonseca2009-05-081-2/+9
| |
| * mesa: make the array object save/remove functions staticBrian Paul2009-05-072-14/+7
| |
| * mesa: clean-up vertex array object VBO unbinding and delete/refcountingBrian Paul2009-05-071-31/+33
| | | | | | | | | | Don't really delete vertex array objects until the refcount hits zero. At that time, unbind any pointers to VBOs.
| * mesa: reference counting for gl_array_objectBrian Paul2009-05-074-14/+83
| | | | | | | | | | Every kind of object that can be shared by multiple contexts should be refcounted.
| * mesa: array object commentsBrian Paul2009-05-071-0/+5
| |
| * mesa: move the NullBufferObj from GLcontext to gl_shared_stateBrian Paul2009-05-0713-41/+50
| | | | | | | | | | Since shared array objects may point to the null/default buffer object, the null/default buffer object should be part of the shared state.
| * mesa: fix comments, s/texture/buffer/Brian Paul2009-05-071-2/+2
| |
| * vbo: in glDraw[Range]Element() code, check for out of bounds indexesBrian Paul2009-05-071-0/+7
| | | | | | | | | | No-op the bad drawing command rather than go out of bounds and render garbage. Print a warning to alert the developer to the bad drawing call.
| * mesa: remove unused gl_buffer_object::OnCard fieldBrian Paul2009-05-072-3/+0
| |
| * mesa: added gl_buffer_object::Written flag (for debug purposes)Brian Paul2009-05-072-0/+7
| | | | | | | | The flag is set when we data has been written into the buffer object.
| * mesa: Compute gl_client_array->_MaxElement during array validationBrian Paul2009-05-074-40/+64
| | | | | | | | | | | | Used to be done in the glVertex/Normal/Color/etc/Pointer() calls but if the VBO was reallocated the size could change. New _NEW_BUFFER_OBJECT state flag.
| * mesa: GLvector4f:: flags is a GLbitfield, update comments too.Brian Paul2009-05-072-5/+5
| |
| * mesa: add storage_count field to GLvector4f. Useful for debugging.Brian Paul2009-05-072-0/+2
| |
| * mesa: use array->BufferObj instead of ctx->Array.ArrayBufferObjBrian Paul2009-05-071-2/+2
| | | | | | | | No difference, but a little more understandable.
| * mesa: added _ElementSize field to gl_client_arrayBrian Paul2009-05-072-0/+3
| | | | | | | | Will be handy for bounds checking later...
| * mesa: use local var to make code a bit more conciseBrian Paul2009-05-071-36/+37
| |
| * mesa: fix/add commentsBrian Paul2009-05-071-3/+2
| |
| * mesa: use _mesa_sizeof_type() in vbo split codeBrian Paul2009-05-071-16/+2
| |
| * mesa: vbo code reformatting, clean-up, commentsBrian Paul2009-05-071-43/+52
| |
| * mesa: add GL_DOUBLE case in _mesa_sizeof_type()Brian Paul2009-05-071-0/+2
| |
| * mesa: in vbo split code, map buffers read-only, not write-onlyBrian Paul2009-05-071-6/+6
| | | | | | | | And use GL_ELEMENT_ARRAY_BUFFER where appropriate.
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-20 08:41:34 +0000