aboutsummaryrefslogtreecommitdiffstats
path: root/src/mesa/drivers/dri/mga/mga_xmesa.c
Commit message (Collapse)AuthorAgeFilesLines
* Add a DRI_ReadDrawable marker extension to signal read drawable capability.Kristian Høgsberg2007-10-111-5/+1
|
* Move media stream counter entry points to new extension.Kristian Høgsberg2007-10-111-3/+2
|
* Move GLX_MESA_swap_frame_usage DRI entry points to the new mechanism.Kristian Høgsberg2007-10-111-1/+1
|
* Move swap_interval to new extension mechanism.Kristian Høgsberg2007-10-101-2/+7
|
* Pull createNewScreen entry point into dri_util.c.Kristian Høgsberg2007-10-101-52/+32
| | | | | | | | This pulls the top level createNewScreen entry point out of the drivers and rewrites __driUtilCreateNewScreen in dri_util.c to be the new entry point. The change moves more logic into the common/ layer and changes the createNewScreen entry point to only be defined in one place.
* Replace open-coded major, minor, and patch version fields with __DRIversionRec.Kristian Høgsberg2007-10-101-2/+2
|
* Remove screenConfigs from __DRIscreen.Kristian Høgsberg2007-10-101-6/+5
| | | | | | | | | | | | The screenConfigs field of __DRIscreen points back to the containing __GLXscreenConfigs struct. This is a serious abstraction violation; it assumes that the loader is libGL and that there *is* a __GLXscreenConfigs type in the loader. Using the containerOf macro, we can get from the __DRIscreen pointer to the containing __GLXscreenConfigs struct, at a place in the stack where the above is a valid assumption. Besides, the __DRI* structs shouldn't hold state other than the private pointer.
* Drop __DRInativeDisplay and pass in __DRIscreen pointers instead.Kristian Høgsberg2007-10-101-11/+11
| | | | | | | | | | | | | Many DRI entry points took a __DRInativeDisplay pointer and a screen index as arguments. The only use for the native display pointer was to pass it back to the loader when looking up the __DRIscreen for the given screen index. Instead, let's just pass in the __DRIscreen pointer directly, which let's drop the __DRInativeDisplay type and the getScreen function. The assumption is now that the loader will be able to retrieve context from the __DRIscreen pointer when necessary.
* remove _tnl_arb_vertex_program_stageBrian2007-04-161-1/+0
|
* call DRI_VALIDATE_DRAWABLE_INFO(), bug 10477Gustavo Pichorim Boiko2007-03-301-1/+2
|
* enable ARB_vertex_buffer_object for more dri driversRoland Scheidegger2007-03-131-0/+2
| | | | | | | ARB_vertex_buffer_object looks like a useful extension even for old chips. The drivers should not need any code to be able to use this extension since they just use mesa's vbo code anyway. Newly enabled for i810, mach64, mga, r128, radeon, savage, sis and unichrome.
* Fix/improve framebuffer object reference counting.Brian2007-03-061-1/+1
| | | | | | | Use _mesa_reference_framebuffer() and _mesa_unreference_framebuffer() functions to be sure reference counting is done correctly. Additional assertions are done too. Note _mesa_dereference_framebuffer() renamed to "unreference" as that's more accurate.
* merge current trunk into vbo branchAlan Hourihane2006-11-021-1/+0
|
* switch remaining drivers over to vboKeith Whitwell2006-10-311-3/+3
|
* Make driDrawableInitVBlank() initialize the sequence number.Michel Dänzer2006-09-281-1/+2
| | | | | This prevents the first wait for vertical blank from timing out when the X server has been running for a long time.
* replace the texture level hack used in radeon/r200 to allow larger textures ↵Roland Scheidegger2006-02-031-1/+2
| | | | 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.
* Instead of calling _mesa_ResizeBuffersMESA() in the Viewport function,Brian Paul2005-09-141-0/+2
| | | | call driUpdateFramebufferSize() when window size/position changes.
* add _tnl_arb_vertex_program_stage to all drivers which already have ↵Roland Scheidegger2005-09-091-0/+1
| | | | _tnl_vertex_program_stage. Fixes crashes when using vertex programs. Tested on r200 only (fix by Keith Whitwell)
* Add new void *addr and __DRIdrawablePrivate parameters toBrian Paul2005-09-041-14/+35
| | | | driNewRenderbuffer().
* Add Egberts fixes for 64bit architecturesAlan Hourihane2005-08-151-1/+5
| | | | | | Add additional checks for the *DRIRec info structure passed in from the device driver. This ensures that things fallback to indirect rendering if the DDX driver has had modifications (i.e. removal of the drmAddress field).
* Fix a == vs !- typo for glx_enable_extensionJon Smirl2005-07-291-1/+1
|
* glxEnableExtension is a platform-specific function exported by the loader.Ian Romanick2005-07-281-9/+7
| | | | Therefore, drivers should not require it to run.
* Major rip-up of internal function insertion interface. The oldmesa_6_3_1Ian Romanick2005-07-281-1/+15
| | | | | | | | | | | | | | | | | | | | | | _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)
* Fixes the glXGetProcAddress portion of the interface. Most of the functionsIan Romanick2005-07-261-28/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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...
* All elements of pre-DRI_NEW_INTERFACE_ONLY are removed. This allowsIan Romanick2005-07-241-41/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* Replace add_newer_entrypoints (src/mesa/main/context.c) withIan Romanick2005-06-301-30/+49
| | | | | | | | | | | | | | | 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
* Adds support for MGA DRM version 3.2.Ian Romanick2005-06-141-13/+22
| | | | | | | | | | | | | | | This patch makes use of two of the new ioctls added in MGA DRM version 3.2. Specifically, the DRM_MGA_SET_FENCE and DRM_MGA_WAIT_FENCE ioctls are used in mgaWaitForFrameCompletion. As a result the MMIO register region and the primary DMA region are *not* mapped (if DRM 3.2 is available). This patch does *not* make use of the new get_param query was added to differentiate between G4x0 cards and G550 cards. That is left to a future update. Xorg bug: 3259 Reviewed by: Eric Anholt
* Add the no_rast debug option, which I used in some testing.Eric Anholt2005-05-301-1/+9
|
* In addition to dead-code removal and other clean-up, bump the required DDXIan Romanick2005-05-181-52/+30
| | | | | | version from 1.0.0 to 1.1.1. 1.1.1 is over a year and a half old at this point, so it should be pretty widespread. This allows the linecomp_sane field to be eliminated from mga_screen_private_s.
* More comments. More dead-code removed. More clean-up.Ian Romanick2005-05-181-4/+6
|
* Remove some unused structure fields, add some comments, and ifdef out someIan Romanick2005-05-121-3/+0
| | | | | dead code. This is just some clean-up work which should not have any functional impact.
* Major check-in of changes for GL_EXT_framebuffer_object extension.Brian Paul2005-05-041-5/+77
| | | | | | | Main driver impacts: - new code for creating the Mesa GLframebuffer - new span/pixel read/write code Some drivers not yet updated/tested.
* Also PUBLICize the config option tableAdam Jackson2004-12-161-1/+1
|
* Mark __driCreateNewScreen PUBLICAdam Jackson2004-12-151-0/+1
|
* uint*t -> u_int*t changesAlan Hourihane2004-12-141-2/+2
|
* Remove _mesa_ResizeBuffersMESA() call from _mesa_set_viewport().Brian Paul2004-11-271-5/+0
| | | | | | | | Now, the driver's Viewport routine should call _mesa_ResizeBuffersMESA() if necessary. Cleaned up code related to GLframebuffer width/height initialization. Set initial viewport/scissor params in _mesa_make_current2(), instead of in the drivers' MakeCurrent functions.
* Use the driFillInModes utility function.Ian Romanick2004-10-041-85/+32
|
* Also export fbconfigs with 0/0 depth/stencil modes. This fixes "driverIan Romanick2004-10-041-4/+6
| | | | claims not to support visual 0xXX" warnings in X.org 6.8.1.
* Minor extension string tweaks. Added support for vertex program extensions.Ian Romanick2004-09-131-3/+21
| | | | Tested with arbvptorus, arbvpwarpmesh, vptorus, and vpwarpmesh.
* Patch removes _SOLO definition needed for mesa-solo. mesa-soloJon Smirl2004-07-041-18/+2
| | | | | uses the NEW_INTERFACE now so _SOLO isn't necessary anymore. Tested with the hardware that I own.
* The required DDX and DRI version numbers were switched. This went unnoticedIan Romanick2004-06-071-2/+2
| | | | | on several drivers (i.e., R200, Radeon, R128, Unichrome) becuase the required DRI and DDX versions were 4.0.0. Mach64 was already fixed.
* Open/Close FullScreen die. unichrome and savage implemented, code is ifdef'd outJon Smirl2004-06-031-9/+0
|
* driCheckDriDdxDrmVersion uses a function that is not available toIan Romanick2004-06-021-2/+10
| | | | | | | | | | | | | | | 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.
* Fix dumb mistake from a previous commit. __driCreateScreen is nowIan Romanick2004-06-011-1/+3
| | | | properly block with '#ifndef DRI_NEW_INTERFACE_ONLY'.
* Convert 'Display *' to '__DRInativeDisplay *'. Only portions of theIan Romanick2004-06-011-2/+2
| | | | | | | | interface that are not *strictly* part of the old interface were changed. Replace GetDrawableInfo type (dri_util.h) with PFNGLXGETDRAWABLEINFOPROC (dri_interface.h). Wrap __driCreateScreen (in drivers that use the new interface) with '#ifndef DRI_NEW_INTERFACE_ONLY'.
* Allow *_dri.so to build in Mesa tree with the 'linux-dri' target.Keith Whitwell2004-04-291-1/+1
|
* call drmUnmapBufs() in mgaDestroyScreen (Tilman Sauerbeck)Brian Paul2004-04-241-0/+2
|
* init mgaScreen->irq (Tilman Sauerbeck)Brian Paul2004-04-231-0/+1
|
* Make sure drivers don't dereference a NULL pointer ifIan Romanick2004-03-261-10/+10
| | | | __driUtilCreateNewScreen returns NULL.
* Adjust includes to help DRI buildJon Smirl2004-03-121-0/+3
|