summaryrefslogtreecommitdiff
path: root/src/mesa/drivers/dri/common/utils.c
AgeCommit message (Collapse)Author
2006-09-28Add helper function to calculate the area of the intersection of two rectangles.Michel Dänzer
2006-08-11Fix long standing bug that prevented newer drivers from working withIan Romanick
older libGL. The data in extension_helper.h erroneous instructed drivers to expect all functions with establised offsets, even those not in the ABI, to have a specific offset allocated. This is just wrong. A function is either in the ABI and has a set offset or a function is not in the ABI and has a re-map offset.
2006-04-03if DDX is -1 don't do DDX checkDave Airlie
2006-04-01These messages really should be printed all the time, users want toDave Airlie
know this not have to set debug for it
2005-08-10Mesa uses the glVertexAttrib*NV functions to implement fixed-functionIan Romanick
attributes in display lists. If a driver doesn't add entry points for GL_NV_vertex_program, it will explode. This patch adds GL_NV_vertex_program to the list of default extensions whose entry points are added by driInitExtensions. Thanks go to Roland Scheidegger for tracking the problem down and suggesting the fix.
2005-08-05Fix recent problems with display lists and other parts of the code.Ian Romanick
CALL_by_offset, SET_by_offset, and GET_by_offset all had various problems. The core issue is that parts of the device-independent code in Mesa assumes that all functions have slots in the dispatch table. This is especially true in the display list code. It will merrilly try to set dispatch pointers for glVertexAttrib1fARB even if GL_ARB_vertex_program is not supported. When the GET/SET/CALL macros are invoked, they would read a 0 from the remap table. The problem is that 0 is the dispatch offset for glNewList! One change is that the remap table is now initialized to be full of -1 values. In addtion, all of the *_by_offset marcos misbehave in an obvious way if the specified offset is -1. SET_by_offset will do nothing, GET_by_offset will return NULL, and CALL_by_offset, since it uses GET_by_offset, will segfault. I also had to add GL_EXT_blend_func_separate to the list of default extensions in all_mesa_extensions (src/mesa/drivers/dri/common/utils.c). Even though many drivers do not export this extension, glBlendFunc is internally implemented by calling glBlendFuncSeparate. Without this addition, glBlendFunc stopped working on drivers (such as mga) that do not export GL_EXT_blend_func_separate. There are still a few assertions / crashes in GL_ARB_vertex_program tests, but I don't think that these are related to any of my changes.
2005-07-28Major rip-up of internal function insertion interface. The oldIan Romanick
_glapi_add_entrypoint has been replaced by a new routine called _glapi_add_dispatch. This new routine dynamically assignes dispatch offsets to functions added. This allows IHVs to add support for extension functions that do not have assigned dispatch offsets. It also means that a driver has no idea what offset will be assigned to a function. The vast majority of the changes in this commit account for that. An additional table, driDispatchRemapTable, is added. Functions not in the Linux OpenGL ABI (i.e., anything not in GL 1.2 + ARB_multitexture) has a fixed offset in this new table. The entry in this table specifies the offset in of the function in the real dispatch table. The internal interface was also bumped from version 20050725 to 20050727. This has been tested with various programs in progs/demos on: radeon (Radeon Mobility M6) r128 (Rage 128 Pro) mga (G400)
2005-07-24All elements of pre-DRI_NEW_INTERFACE_ONLY are removed. This allowsIan Romanick
1,402 lines of code to be removed from Mesa (drivers and libGL). The big winner is dri_util.c. Primary changes are: 1. Remove all "deprecated" entry-points from the various structures in dri_interface.h. 2. Rename the remaining fields to removed "version numbers." So, bindContext3 becomes bindContext. Functions with "New" in the name (e.g., CreateNewContext) were *not* changed, but that is an option. Having "New" in the name is less annoying to me than having "3" in the name. 3. Remove all compatibility code that handles cases where the driver or the loader is too old to support the latest interfaces. 4. Append the API version to the __driCreateNewScreen function name. This is currently done by hand. In the future (i.e., the next time we make an incompatible change to the interface) we'll want to come up with a better way to do this. This prevents old loaders from being able to load new (incompatible) drivers. 5. Bump the API version to 20050722. All drivers (by way of dri_util.c) require this version. 6. All drivers are *required* to expose GLX_SGIX_fbconfig and GLX_OML_swap_method (or the moral equivalents). Support for these functions in implicit in the use of the "new" interface. 7. Some cases still exist that need to be compiled differently in a loader or core Mesa versus in a driver. These are identified by the define IN_DRI_DRIVER.
2005-06-30Replace add_newer_entrypoints (src/mesa/main/context.c) withIan Romanick
device-specific code. A new Python script (src/mesa/glapi/extension_helper.py) generates a list of all entry-points for all known extensions. Each driver the selects only the extensions that it needs and enables the via either driInitExtensions or driInitSingleExtension. This code has been compile-tested on a drivers, but has only been run-tested on mga and i915 (on i830 hardware). These changes were discussed at length on the mesa3d-dev mailing list. http://marc.theaimsgroup.com/?t=111947074700001&r=1&w=2
2005-03-22Calculate haveAccumBuffer, haveDepthBuffer and haveStencilBuffer inKeith Whitwell
driFillInModes().
2005-01-26new version check to allow to test for a range of ddx major versions, ↵Roland Scheidegger
instead of just one major version
2004-12-14uint*t -> u_int*t changesAlan Hourihane
2004-10-13Initial support for PowerPC specific code in Mesa and DRI drivers. DRIIan Romanick
drivers built on PowerPC systems should now show things like "PowerPC" or "PowerPC/Altivec" in the GL_RENDERER string. The VMX moniker is used for Altivec/Velocity Engine/VMX SIMD additions. I chose this not because I work for IBM but because it's a LOT shorter to type. :)
2004-10-13Refactor the code in driGetRendererString a bit to make it easier toIan Romanick
add support for features of non-x86 CPU types.
2004-07-04Patch removes _SOLO definition needed for mesa-solo. mesa-soloJon Smirl
uses the NEW_INTERFACE now so _SOLO isn't necessary anymore. Tested with the hardware that I own.
2004-06-15Fix a couple typeos in the tables for driFillInModes.Ian Romanick
2004-06-03Add a new function, driFillInModes, that is to be used by drivers toIan Romanick
create the set of support __GLcontextModes. This should replace the current driver-specific fill_in_modes functions.
2004-06-02driCheckDriDdxDrmVersion uses a function that is not available toIan Romanick
drivers when DRI_NEW_INTERFACE_ONLY is defined. #ifndef it away in that situation. Add a new function, driCheckDriDdxDrmVersion2, that is passed in the version information that is already supplied to __driCreateNewScreen. Part of the reason that information is supplied to __driCreateNewScreen is so that the driver doesn't have to make those calls to get it! Modify all drivers that support the new interface to use the new function instead of the old. As soon as all drivers support the new interface, driCheckDriDdxDrmVersion can be removed.
2004-04-26bring over build fixes from stable branchAlan Hourihane
2004-03-15extend SOLO code so the DDX version isn't checkedDave Airlie
2003-12-11add driClipRectToFramebuffer helper functionKeith Whitwell
2003-12-04build fixAlan Hourihane
2003-08-06Shared dri driver resourcesKeith Whitwell