summaryrefslogtreecommitdiff
path: root/src/mesa/drivers/dri/mga/mga_xmesa.c
AgeCommit message (Collapse)Author
2006-09-28Make driDrawableInitVBlank() initialize the sequence number.Michel Dänzer
This prevents the first wait for vertical blank from timing out when the X server has been running for a long time.
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.
2005-09-14Instead of calling _mesa_ResizeBuffersMESA() in the Viewport function,Brian Paul
call driUpdateFramebufferSize() when window size/position changes.
2005-09-09add _tnl_arb_vertex_program_stage to all drivers which already have ↵Roland Scheidegger
_tnl_vertex_program_stage. Fixes crashes when using vertex programs. Tested on r200 only (fix by Keith Whitwell)
2005-09-04Add new void *addr and __DRIdrawablePrivate parameters toBrian Paul
driNewRenderbuffer().
2005-08-15Add Egberts fixes for 64bit architecturesAlan Hourihane
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).
2005-07-29Fix a == vs !- typo for glx_enable_extensionJon Smirl
2005-07-28glxEnableExtension is a platform-specific function exported by the loader.Ian Romanick
Therefore, drivers should not require it to run.
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-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-14Adds support for MGA DRM version 3.2.Ian Romanick
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
2005-05-30Add the no_rast debug option, which I used in some testing.Eric Anholt
2005-05-18In addition to dead-code removal and other clean-up, bump the required DDXIan Romanick
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.
2005-05-18More comments. More dead-code removed. More clean-up.Ian Romanick
2005-05-12Remove some unused structure fields, add some comments, and ifdef out someIan Romanick
dead code. This is just some clean-up work which should not have any functional impact.
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.
2004-12-16Also PUBLICize the config option tableAdam Jackson
2004-12-15Mark __driCreateNewScreen PUBLICAdam Jackson
2004-12-14uint*t -> u_int*t changesAlan Hourihane
2004-11-27Remove _mesa_ResizeBuffersMESA() call from _mesa_set_viewport().Brian Paul
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.
2004-10-04Use the driFillInModes utility function.Ian Romanick
2004-10-04Also export fbconfigs with 0/0 depth/stencil modes. This fixes "driverIan Romanick
claims not to support visual 0xXX" warnings in X.org 6.8.1.
2004-09-13Minor extension string tweaks. Added support for vertex program extensions.Ian Romanick
Tested with arbvptorus, arbvpwarpmesh, vptorus, and vpwarpmesh.
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-07The required DDX and DRI version numbers were switched. This went unnoticedIan Romanick
on several drivers (i.e., R200, Radeon, R128, Unichrome) becuase the required DRI and DDX versions were 4.0.0. Mach64 was already fixed.
2004-06-03Open/Close FullScreen die. unichrome and savage implemented, code is ifdef'd outJon Smirl
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-06-01Fix dumb mistake from a previous commit. __driCreateScreen is nowIan Romanick
properly block with '#ifndef DRI_NEW_INTERFACE_ONLY'.
2004-06-01Convert 'Display *' to '__DRInativeDisplay *'. Only portions of theIan Romanick
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'.
2004-04-29Allow *_dri.so to build in Mesa tree with the 'linux-dri' target.Keith Whitwell
2004-04-24call drmUnmapBufs() in mgaDestroyScreen (Tilman Sauerbeck)Brian Paul
2004-04-23init mgaScreen->irq (Tilman Sauerbeck)Brian Paul
2004-03-26Make sure drivers don't dereference a NULL pointer ifIan Romanick
__driUtilCreateNewScreen returns NULL.
2004-03-12Adjust includes to help DRI buildJon Smirl
2004-03-12Adjust mga drivers to remove redundant h file for sarea and IOCTLsJon Smirl
2004-02-27Create all the right modes for 16-bit screens.Ian Romanick
2004-02-26added _tnl_allow_vertex/pixel_fog() callsBrian Paul
2004-02-12Enable use of new DRI interface in MGA driver.Ian Romanick
2004-01-26Make the drivers using the common texmem code work with NewTextureObjectFelix Kuehling
in Mesa. This is analogous to changes idr made to the r200 driver. Patch submitted by Andreas Stenglein.
2004-01-21Silence some compiler warnings.Ian Romanick
2004-01-20Before calling _mesa_create_context(), initialize a dd_function_table structBrian Paul
by calling _mesa_init_driver_functions() and then plugging in the driver- specific functions. In particular, make sure ctx->Driver.NewTextureObject points to the appropriate driver function so that _all_ texture objects are augmented with the driver-specific data. Put in a bunch of assertions in the texture-related driver functions that texObj->DriverData is valid. Remove old dead code in near future.
2004-01-18Change get_ust_nop()'s parameter from int64_t to uint64_t to silence warnings.Brian Paul
2004-01-12Removed redundant extension strings. The Mesa extension mechanismIan Romanick
automatically enables "duplicate" extensions without the driver explicitly enabling them.
2003-12-12applied Felix's patch for configuration systemBrian Paul
2003-12-12set MaxTextureImageUnits, MaxTextureCoordUnitsKeith Whitwell
2003-12-08fix bogus assertion that checked for an empty texture heap list beforeAlan Hourihane
deleting the textures. Essentially move the assertion after the destruction of the heap.
2003-12-05bring over latest mga DRI driver from DRI trunkAlan Hourihane
2003-11-24Import vtx-0-2-branchKeith Whitwell