summaryrefslogtreecommitdiff
path: root/src/mesa/drivers/dri/common
AgeCommit message (Collapse)Author
2010-08-27dri: Get prototype for _mesa_destroy_compiler().Eric Anholt
Bug #29665.
2010-08-18glsl2: Free the shader compiler at dri screen destruction.Eric Anholt
Hooray, we can valgrind again without adding suppressions. This also adds an interface for use by an implementation of glReleaseShaderCompiler().
2010-08-18dri2: Clean up the common dri2 options at screen destroy.Eric Anholt
2010-08-13Merge branch 'master' into glsl2Ian Romanick
2010-08-13mesa: Avoid using c++ keyword in dri_util.h when compiled with c++.Eric Anholt
2010-07-29dri: Add missing header to dri_metaops.c.Vinson Lee
Add context.h for FLUSH_VERTICES symbol.
2010-07-19glx: Remove support for MESA_swap_frame_usageKristian Høgsberg
The extension never worked, the implementation returns GLX_BAD_CONTEXT when enabling the frame tracking.
2010-06-10mesa: rename src/mesa/shader/ to src/mesa/program/Brian Paul
2010-06-10mesa: move arbprogram.[ch] to main/Brian Paul
2010-06-10i965: Add support for GL_ALPHA framebuffer objects.Eric Anholt
2010-05-31gallium: fix TFP on galliumDave Airlie
This fixes an uninitialised value use in the dri2 st when doing TFP. It uses the driContextPriv which isn't initialised at alloc time. Signed-off-by: Dave Airlie <airlied@redhat.com>
2010-05-11intel: Drop viewport hack when we canKristian Høgsberg
2010-05-03swrast: Correct include for mtypes.hJakob Bornecrantz
2010-05-02Update drisw state tracker to use new API aware context createXavier Chantry
Even though swrast defines its own __DriverAPIRec it still shares the driCreateNewContext() implementation from dri_util.c. So the CreateContext prototypes have to match in the two __DriverAPIRecs. Reviewed-by: Jakob Bornecrantz <jakob@vmware.com> Signed-off-by: Xavier Chantry <chantry.xavier@gmail.com>
2010-05-02Merge branch 'gles2-2'Kristian Høgsberg
Conflicts: src/mesa/drivers/dri/common/dri_util.h
2010-04-28dri: Add DRI entrypoints to create a context for a given APIKristian Høgsberg
2010-04-27dri_util: Assume error checking is done properly in glXMakeCurrentJakob Bornecrantz
In short what the code did before: __DRIscreen *psp = NULL; if (pcp) psp = pcp->psb; assert(psp); if (psp->stuff) other_stuff(); return psb->even_more(pcp); Remove all that stupid checking which still segfaults/asserts later on and just do what we do in driUnbindContext. Also limited testing show libGL never call driUnbindContext or driBindContext with cPriv == NULL.
2010-04-24dri: Remove unnecessary header.Vinson Lee
2010-04-22DRI2/GLX: check for vblank_mode in DRI2 GLX codeJesse Barnes
Re-add support for the vblank_mode environment and configuration variable. Useful for benchmarking and app control.
2010-04-22DRI2: add config query extensionJesse Barnes
Add a new DRI2 configuration query extension. Allows for DRI2 client code to query for common DRI2 configuration options.
2010-04-19Merge branch '7.8'Jesse Barnes
2010-04-19mesa: Use __OpenBSD__ to check for OpenBSD.Matthieu Herrb
Signed-off-by: Brian Paul <brianp@vmware.com>
2010-03-30dri: Drop another unused __DRIscreen fieldKristian Høgsberg
2010-03-30dri: Drop the unused dummyContextKristian Høgsberg
2010-03-30dri: Drop an unused __DRIcontext fieldKristian Høgsberg
2010-03-30drisw: fix use after free (bug 27370)George Sapountzis
2010-03-26dri/common: add comment about DRISW wrt DRI1 / DRI2George Sapountzis
2010-03-25drisw_util: add fields for gallium swrast_driGeorge Sapountzis
2010-03-23dri: fix dri_test.c for non-TLS buildLuca Barbieri
_glapi_Context and _glapi_Dispatch have different constness between TLS and non-TLS builds.
2010-03-23dri: add _glthread_GetID to dri_test.c dummy glapiLuca Barbieri
2010-03-23dri: make unresolved symbol test link work even without a libGL.soLuca Barbieri
Currently the test link uses -lGL to define the glapi symbols. This makes it impossible to build DRI drivers on systems without Mesa installed and without building the libGL from the Mesa tree first. Some automated build systems trigger this problem. This commit removes -lGL and instead adds a dummy implementation of glapi to dri_test.c This, along with Kristian's commit, should fix all known regressions due to the addition of unresolved symbol checking.
2010-03-23dri: test whether the built drivers have unresolved symbolsLuca Barbieri
This is a different approach to solving this problem that the patch I previously posted, and unlike that, should not cause any problems. Right now undefined symbols in DRI drivers will still allow the build to succeed. As a result, people modifying drivers they cannot test risk creating unloadable drivers with no easy way of automatically avoiding it. For instance, the modifications to nv50 for context transfers caused such an issue recently. Unfortunately, just adding -Wl,--no-undefined doesn't work, because the DRI drivers depend on glapi symbols, but do not depend on libGL.so.1 Adding -lGL is not the correct solution since DRI drivers are not loaded just by libGL, but also by X and possibly by other clients. So, this patch simply tries to build an executable linked to the DRI driver and to libGL. If the DRI driver contains any undefined symbols not satisfied by its dependencies or by libGL, this will fail. This solution does not alter the built drivers, and does not significantly slow down the build process. All classic DRI drivers as well as all the Gallium drivers with configure options compiled successfully with this change. Thanks to Xavier Chantry <chantry.xavier@gmail.com> and Michel Daenzer <michel@daenzer.net> for helping with this. Signed-off-by: Luca Barbieri <luca@luca-barbieri.com> Acked-by: Brian Paul <brian.e.paul@gmail.com>
2010-03-21rename dri_sw to drisw_util for consistencyGeorge Sapountzis
2010-03-15dri/common: mv __driUtilMessage to utils.cGeorge Sapountzis
allows to link with xmlconfig without dri_util, and has nothing drm-specific.
2010-03-15dri/swrast: drop mtypes.h from dri_swGeorge Sapountzis
2010-03-15dri/swrast: port to dri_sw (drawable)George Sapountzis
2010-03-15dri/swrast: port to dri_sw (context)George Sapountzis
2010-03-15dri: add dri_sw.c helperGeorge Sapountzis
This is dri_util.c stripped from the drm-specific bits and will be used for both classic and gallium swrast_dri.so
2010-03-12Grammar and spelling fixesJeff Smith
Signed-off-by: Jeff Smith <whydoubt@yahoo.com> Signed-off-by: Brian Paul <brianp@vmware.com>
2010-03-04DRI: Put back missing break-statementIan Romanick
The break in the __DRI_ATTRIB_RENDER_TYPE case was accidentally removed in commit 5cf2c5851bcd29c2d53bb04ab692b4b156f5a74d. This puts it back. Signed-off-by: Ian Romanick <ian.d.romanick@intel.com>
2010-03-03DRI: Remove support for color-index visualsIan Romanick
Signed-off-by: Ian Romanick <ian.d.romanick@intel.com>
2010-02-27dri: Remove dead code.Vinson Lee
2010-02-27dri: Add assert to check for null pointer dereference.Vinson Lee
2010-02-27dri: Assert pointer is not null before dereferencing.Vinson Lee
2010-02-26remove hack for miniglx from dri/utils.cGeorge Sapountzis
2010-02-24dri: remove old assertion (see bug 26734)Brian Paul
(cherry picked from commit 293f4d51b473783d5c5ab773a1c438e0a2fe46f2)
2010-02-24intel: Implement DRI image extensionKristian Høgsberg
2010-02-19Replace _mesa_malloc, _mesa_calloc and _mesa_free with plain libc versionsKristian Høgsberg
2010-02-17intel: Implement the DRI2 invalidate function properlyKristian Høgsberg
This uses a stamp mechanisms to mark the DRI drawable as invalid. Instead of immediately updating the buffers we just bump the drawable stamp and call out to DRI2GetBuffers "later". "Later" used to be at LOCK_HARDWARE time, and this patch brings back callouts at the points where we used to call LOCK_HARDWARE. A new function, intel_prepare_render(), is called where we used to call LOCK_HARDWARE, and if the buffers are invalid, we call out to DRI2GetBuffers there. This lets us invalidate buffers only when notified instead of on every glViewport() call. If the loader calls the DRI invalidate entrypoint, we disable viewport triggered buffer invalidation. Additionally, we can clean up the old viewport mechanism a bit, since we can just invalidate the buffers and not worry about reentrancy and whatnot.
2010-02-16dri2: Event driven buffer validation.Francisco Jerez
When a buffer invalidation event is received from the X server, the "invalidate" hook of the DRI2 flush extension is executed: A generic implementation (dri2InvalidateDrawable) is provided that just bumps the "pStamp" sequence number in __DRIdrawableRec. For old servers not supporting buffer invalidation events, the invalidate hook will be called before flushing the fake front/back buffer (that's typically once per frame -- not a lot worse than the situation we were in before). No effort has been made on preserving backwards compatibility with version 2 of the flush extension, but I think it's acceptable because AFAIK no released stack is making use of it. Signed-off-by: Kristian Høgsberg <krh@bitplanet.net>