summaryrefslogtreecommitdiffstats
path: root/src/mesa/drivers
Commit message (Collapse)AuthorAgeFilesLines
* actually free the renderbuffer in xmesa_delete_renderbuffer(), fixes a ↵Brian Paul2005-08-091-1/+5
| | | | memory leak
* _mesa_free_framebuffer_data() call frees the renderbuffers, no need to call ↵Brian Paul2005-08-091-4/+0
| | | | the Delete methods after
* free context structure (bug 1252316) and s/free/_mesa_free/Brian Paul2005-08-091-6/+7
|
* Since glcontextmodes.[ch] are no longer used in the DRI drivers, removed theIan Romanick2005-08-082-6/+6
| | | | IN_DRI_DRIVER cruft. This was suggested by George Fufutos.
* fix up color tiling in miniglx radeon server codeDave Airlie2005-08-081-15/+34
|
* Remove platform specific bits from radeon_egl.cJon Smirl2005-08-081-2/+0
|
* Dike out the linux-specific EGL bits unless it's a linux build.Eric Anholt2005-08-081-1/+5
|
* Enable EGL support in 'linux-dri' configJon Smirl2005-08-071-5/+7
|
* Fix card_extensions by following corresponding r200 code.Vladimir Dergachev2005-08-061-50/+12
| | | | | Fix suggested by Ian Romanick. R300 driver now works without segfault.
* Fixes bugzillla #812.Ian Romanick2005-08-051-8/+0
| | | | | | | 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.
* remove the drmAddressAlan Hourihane2005-08-051-1/+0
|
* Fix recent problems with display lists and other parts of the code.Ian Romanick2005-08-051-1/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* More EGL prep. No impact on anything outside of EGLJon Smirl2005-08-054-10/+19
|
* New files for radeon egl driver.Jon Smirl2005-08-041-0/+980
| | | | Still a work in progress.
* Add color tiling support to miniglx for radeonDave Airlie2005-08-033-2/+81
| | | | (Stephane Marchesin + Dave Airlie)
* Leave the AGP_BASE code in. It is pointless to bump the interfaceJon Smirl2005-07-291-0/+4
| | | | for X on a miniglx fix. It can be removed later.
* Remove OUTREG(RADEON_AGP_BASE, info->ringHandle); from DRI driverJon Smirl2005-07-291-4/+0
| | | | Code is already in DRM driver to do this.
* Commit Ian's fixes from Bug 3877Jon Smirl2005-07-292-4/+4
| | | | | I have tested these on miniglx and they seem to be working. I'm sure Dave will give them a better test.
* Fix a == vs !- typo for glx_enable_extensionJon Smirl2005-07-298-9/+9
|
* Use the routines supplied in the __DRIinterfaceMethods structure to create aIan Romanick2005-07-283-6/+3
| | | | | destroy __GLcontextModes structures. This eliminates the need for DRI drivers to ever link with glcontextmodes.c.
* glxEnableExtension is a platform-specific function exported by the loader.Ian Romanick2005-07-289-85/+66
| | | | Therefore, drivers should not require it to run.
* Major rip-up of internal function insertion interface. The oldmesa_6_3_1Ian Romanick2005-07-2829-867/+1041
| | | | | | | | | | | | | | | | | | | | | | _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)
* test for the proper drm version, at least 1.17 is requiredRoland Scheidegger2005-07-271-1/+1
|
* typoAlan Hourihane2005-07-261-1/+1
|
* support GLX_DIRECT_COLOR in 1.4.0Alan Hourihane2005-07-261-3/+1
|
* Remove the last remnants of GLX_BUILT_IN_XMESA. This allows the removal ofIan Romanick2005-07-263-76/+1
| | | | the evil, ugly GLX_PREFIX macro as well.
* Bump the required ddx to 1.4.0 as drmAddress has been removed so that 32/64bitAlan Hourihane2005-07-261-4/+12
| | | | combinations work.
* Fixes the glXGetProcAddress portion of the interface. Most of the functionsIan Romanick2005-07-2632-390/+209
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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...
* Fix bug 1858 - array subscript out of range in gamma driver.Brian Paul2005-07-263-3/+2
| | | | | | Set ctx->Const.MaxTextureLevels = GAMMA_TEX_MAXLEVELS = 12 Remove bogus WRITE(level 12). Max gamma texture size is 2kx2k (note: 2k = 1 << (MaxLevels - 1))
* All elements of pre-DRI_NEW_INTERFACE_ONLY are removed. This allowsIan Romanick2005-07-2425-1215/+198
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* ----------------------------------------------------------------------Jouk Jansen2005-07-221-0/+3
| | | | | | | | | | Committing in . _mesa_sprintf crashes on OpenVMS -> replaced it by the OS-supplied sprintf Modified Files: Mesa/src/mesa/drivers/x11/fakeglx.c ----------------------------------------------------------------------
* make i810PrintSetupFlags() static, first param constBrian Paul2005-07-212-4/+1
|
* Clean up warnings in r300 code by making some symbols static, adding prototypesEric Anholt2005-07-2011-18/+36
| | | | | for others, and being cleaner with types in fragment/vertex program structures. One warning in r300_shader.c is still concerning.
* include driverfuncs.hBrian Paul2005-07-191-2/+0
|
* Fix the FFB driver for the renderbuffer changesAlan Hourihane2005-07-188-94/+316
| | | | Support NEW INTERFACE as well
* Wrap every place that accesses a dispatch table with a macro. A new script-Ian Romanick2005-07-185-90/+99
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | generated file, called src/mesa/glapi/dispatch.h, is added. This file contains three macros for each API function. It contains a GET, a SET, and a CALL. Each of the macros take a pointer to the context and a pointer to the dispatch table. In several threads on mesa3d-dev we discussed replacing _glapi_add_entrypoint with a new function called _glapi_add_dispatch. For this discussion, the important difference between the two is that the caller of _glapi_add_dispatch does *not* know what the dispatch offset will be at compile time. Because of this callers need to track the dispatch offset returned by _glapi_add_dispatch. http://marc.theaimsgroup.com/?t=111947074700001&r=1&w=2 The downside is that driver code then has to access the dispatch table two different ways. It accesses it using structure tags (e.g., exec->Begin) for functions with fixed offsets and via a remap table (e.g., exec[ remap->NewExtensionFunction ]) for functions without fixed offsets. Yuck! Using the macros allows both types of functions to be accessed identically. If a driver needs to set a pointer for Begin, it does 'SET_Begin(ctx, exec, my_begin_function)'. If it needs to set a pointer for NewExtensionFunction, it does 'SET_NewExtensionFunction(ctx, exec, my_NewExtensionFunction_function)'. Furthermore, if at some point in the future a static offset is assigned for NewExtensionFunction, only the macros need to change (instead of every single place that accesses a table for that function). This code differs slightly from the originally posted patches in that the CALL, GET, and SET marcos no longer take a context pointer as a parameter. Brian Paul had suggested that the remap table could be stored as a global since it would be set at CreateScreen time and would be constant for all contexts. This change reflects that feedback. http://marc.theaimsgroup.com/?t=112087194700001&r=1&w=2
* XMesaResizeBuffers needs separate paths for client and server buildsAdam Jackson2005-07-161-0/+7
|
* strip out vestigial #ifdef HAVE_CONFIG_H stanzas, they're confusing theAdam Jackson2005-07-161-6/+0
| | | | modular X build
* disable call to via_sse_memcpy() until it's fixedmesa_20050715Brian Paul2005-07-151-1/+7
|
* remove duplicate "User disable" stringBrian Paul2005-07-151-1/+0
|
* replace gcc with $(CC) (Egbert Eich)Brian Paul2005-07-151-4/+2
|
* added a few more fallbackStrings (Andreas Stenglein)Brian Paul2005-07-141-1/+5
|
* Re-enable r200InitSpanFuncs, which was ifdefed out (probably by mistake?),Roland Scheidegger2005-07-061-2/+0
| | | | | so r200SetBuffer, r200SpanRenderStart and r200SpanRenderFinish get called again. Bugzilla #3705, #3706.
* Expose the fact that we do not do either selection of feedback buffers - ↵Vladimir Dergachev2005-07-022-0/+11
| | | | either with software or hardware rendering.
* Adding RV350_NJ ID.Jerome Glisse2005-07-011-0/+2
|
* Adapt extension string to new GL dispatch schema proposedJerome Glisse2005-07-011-1/+48
| | | | | | by Idr. This patch is based on Idr patch to radeon driver. Change #if 1 to #if 0 (r300_context.c:l69) for old dispatch tab.
* Fix a prototypeKarl Schultz2005-07-011-5/+5
|
* convert sis and radeon driver to use spantmp2 instead of spantmp template. ↵Roland Scheidegger2005-07-013-317/+27
| | | | Remove old (pre-renderbuffer) span code instead of converting that too. Remove this old code from mach64 (the dead code was not fully converted to spantmp2 previously) too.
* Remove NEW_RENDERBUFFER stuff.Brian Paul2005-07-012-15/+7
| | | | | Now, OLD_RENDERBUFFER marks code that needs to eventually be removed when all the drivers are updated to no longer need the SetBuffer() function.
* remove common macros used in the span functions of most drivers from the ↵Roland Scheidegger2005-07-0119-475/+124
| | | | 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.
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-26 21:01:12 +0000