summaryrefslogtreecommitdiff
path: root/src/mesa/drivers/dri/common
AgeCommit message (Collapse)Author
2006-03-26merge from texman branchBrian Paul
2006-03-23fix coverity 926: use before NULL checkDave Airlie
2006-03-17Don't use glx_ansic.h functions (__glXMemset).Kristian Høgsberg
2006-03-01Added glBlitFramebufferEXT function.Brian Paul
2006-02-09remove the test for XFree86Server from prev patch (bug 5835)Brian Paul
2006-02-08include dix-config.h (Mike Harris) (bug 5835)Brian Paul
2006-02-03replace the texture level hack used in radeon/r200 to allow larger textures ↵Roland Scheidegger
with different methods to calculate the announced maximum texture sizes. Default is still the same (that is, radeon/r200 default to not announce anything which might not fit, i830/i915 default to 1 texture must fit). Bug #5785.
2006-01-30fix broken assertions so dri drivers compile with -DDEBUG (replace ↵Roland Scheidegger
GL_STENCIL_INDEX8 with GL_STENCIL_INDEX8_EXT). Fix potential problem with drivers which use 32bit z buffers.
2005-12-07Updates for GL_EXT_timer_query:Brian Paul
New GLint64EXT and GLuint64EXT types (use C99's long long types). New glGetQueryObject[u]i64vEXT() functions.
2005-11-29assorted fixes for server-side direct rendering (bug 5199)Brian Paul
2005-11-28Remove the many aliases for 'struct mem_block' in mm.hKeith Whitwell
2005-10-28Silence gcc-4 warnings.Aapo Tahkola
2005-10-27Add support for HW stencil spans, mirroring the depth spans support. Used forEric Anholt
Rage 128 stencil support.
2005-10-18Add _mesa_exec_malloc() and _mesa_exec_free() for allocatingKeith Whitwell
executable memory. Based on Thomas Hellstrom's patch. TODO: glapi.c also needs this, but cannot access this code.
2005-10-15fix two bugs wrt calculating max possible texture sizes for texture ↵Roland Scheidegger
rectangles/cube maps.
2005-09-22Replace gl_renderbuffer.ComponentSizes[] with separate RedBits, GreenBits,Brian Paul
BlueBits, etc fields.
2005-09-14added driUpdateFramebufferSize()Brian Paul
2005-09-08use an explicit reserved field, rather than magic number in boundKeith Whitwell
2005-09-08Fix the comment for the 'bound' field: it's a bitmask, not an index.Brian Paul
In driTexturesGone(), set bound = 0, not 99.
2005-09-04just formatting clean-upsBrian Paul
2005-09-04Add new void *addr and __DRIdrawablePrivate parameters toBrian Paul
driNewRenderbuffer().
2005-09-04Combine GET_DST_PTR and GET_SRC_PTR into just GET_PTR.Brian Paul
2005-09-04Added InitPointers helper functionBrian Paul
2005-09-04replace assertion with a conditional returnBrian Paul
2005-09-03added flippedData field for page flipping, code to flip stereo color buffersBrian Paul
2005-09-03added SetStencil/DepthPointer functionsBrian Paul
2005-09-01added driFlipRenderbuffers()Brian Paul
2005-09-01added a few more fields to help with DRI driversBrian Paul
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-08Since glcontextmodes.[ch] are no longer used in the DRI drivers, removed theIan Romanick
IN_DRI_DRIVER cruft. This was suggested by George Fufutos.
2005-08-05Fixes bugzillla #812.Ian Romanick
The weak version of _glapi_DispatchTSD was removed from dri_util.c. As stated in the bug report, this was only needed to support versions of libGL that did not have this symbol. Versions of libGL without this symbol are no longer supported at all, so it is totally irrelevant.
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-29Commit Ian's fixes from Bug 3877Jon Smirl
I have tested these on miniglx and they seem to be working. I'm sure Dave will give them a better test.
2005-07-28Use the routines supplied in the __DRIinterfaceMethods structure to create aIan Romanick
destroy __GLcontextModes structures. This eliminates the need for DRI drivers to ever link with glcontextmodes.c.
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-26Fixes the glXGetProcAddress portion of the interface. Most of the functionsIan Romanick
that are currently obtained via glXGetProcAddress and all of the XF86DRI functions are replaced with a funciton table. This table will be passed to __driCreateNewScreen. One of the functions in the table is getProcAddress. This allows some loaders to expose functionality not in all loaders. This will be immediatly used for glxEnableExtension (formerly known to drivers as __glXScrEnableExtension). libGL (and in the future libglx) expose this function so that drivers can enable GLX extensions. libEGL should exposed eglEnableExtension to enable EGL extensions. The same function cannot be used for both because the extensions have different names and (possibly) different semantics. Drivers can optionally use one, both, or neither. The key parts are in the __DRIinterfaceMethodsRec structure in dri_interface.h. A pointer to one of these structures is passed into __driCreateNewScreen. Because of this, the version of the API is bumped to 20050725. Since the previous version(s) were never in a release, their existance is erased. I was actually a little surprised by how much code this cuts from the drivers. A lot of glXGetProcAddress calls disappear, and a lot of version checks go with them. Nice. The one thing I'm not sure of is removing __glXInitialize. For some reason that function was in the glXGetProcAddress table, but *nothing* in the Mesa tree used it. Did something with DRI conf. use this function? It seems odd...
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-07-01remove common macros used in the span functions of most drivers from the ↵Roland Scheidegger
individual drivers and put them in common code. It is still possible for a driver to define its own macros if it has special needs. This affects CLIPPIXEL, CLIPSPAN, HW_CLIPLOOP, HW_ENDCLIPLOOP, and for drivers using the spantmp2 template also GET_SRC_PTR and GET_DST_PTR.
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-06-04added commentBrian Paul
2005-06-02oops, undo previous changeBrian Paul
2005-06-02start removing old (pre-renderbuffer) span codeBrian Paul
2005-05-19remove the XFree86 ID lineBrian Paul
2005-05-12Add check for mask == NULL to the one routine missing it.Keith Whitwell
2005-05-05fix for renderbuffer (Andreas Stenglein)Brian Paul
2005-05-05Fix up origin in dri/fb driverJon Smirl
Calculated fbBPP
2005-05-04Major check-in of changes for GL_EXT_framebuffer_object extension.Brian Paul
Main driver impacts: - new code for creating the Mesa GLframebuffer - new span/pixel read/write code Some drivers not yet updated/tested.
2005-04-25Minor changes to make linux-solo build againJon Smirl
2005-04-22Added a French translation of option descriptions by Stephane Marchesin.Felix Kuehling
2005-04-13Revert revision 1.13. This allows server-side libGLcore (in X.org) to buildIan Romanick
with Mesa CVS. This change was wrong in the first place, and the issue that necessitated it has been resolved. For more background on the problem see: http://marc.theaimsgroup.com/?l=mesa3d-dev&m=111333880529935&w=2