summaryrefslogtreecommitdiffstats
path: root/include/GL
Commit message (Collapse)AuthorAgeFilesLines
* remove old/unused foomesa.h example headerBrian Paul2008-06-041-76/+0
|
* Assorted Windows fixes (Karl Schultz)Brian Paul2008-05-291-1/+1
|
* drop GLcoreGeorge Sapountzis2008-05-231-73/+0
|
* Add DRI driver that uses the mesa swrast module.George Sapountzis2008-05-201-0/+57
|
* glcore: build from mesaGeorge Sapountzis2008-04-231-0/+73
|
* DRI interface changes and DRI2 direct rendering support.Kristian Høgsberg2008-03-312-205/+215
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add DRI2 direct rendering support to libGL and add DRI2 client side protocol code. Extend the GLX 1.3 create drawable functions in glx_pbuffer.c to call into the DRI driver when possible. Introduce __DRIconfig, opaque struct that represents a DRI driver configuration. Get's rid of the open coded __GLcontextModes in the DRI driver interface and the context modes create and destroy functions that the loader was requires to provide. glcore.h is no longer part of the DRI driver interface. The DRI config is GL binding agnostic, that is, not specific to GLX, EGL or other bindings. The core API is now also an extension, and the driver exports a list of extensions as the symbol __driDriverExtensions, which the loader must dlsym() for. The list of extension will always include the DRI core extension, which allows creating and manipulating DRI screens, drawables and contexts. The DRI legacy extension, when available, provides alternative entry points for creating the DRI objects that work with the XF86DRI infrastructure. Change DRI2 client code to not use drm drawables or contexts. We never used drm_drawable_t's and the only use for drm_context_t was as a unique identifier when taking the lock. We now just allocate a unique lock ID out of the DRILock sarea block. Once we get rid of the lock entirely, we can drop this hack. Change the interface between dri_util.c and the drivers, so that the drivers now export the DriverAPI struct as driDriverAPI instead of the InitScreen entry point. This lets us avoid dlsym()'ing for the DRI2 init screen function to see if DRI2 is supported by the driver.
* updated to version 40Brian2008-03-251-3/+14
|
* fix wrong values for GL_READ/DRAW_FRAMEBUFFER_BINDING_EXT tokensBrian2008-03-241-2/+2
|
* DRI2: Make setTexBuffer take a __DRIdrawable instead of a BO handle.Kristian Høgsberg2008-03-091-7/+5
| | | | | | | | | | | | | | | | | This fixes a problem where texturing from the same Pixmap more than once per batchbuffer would hang the DRI driver. We just use the region associated with the front left renderbuffer of the __DRIdrawable for texturing, which avoids creating different regions for the same BO. This change also make GLX_EXT_texture_from_pixmap work for direct rendering, since tracking the __DRIdrawable -> BO handle now uses the standard DRI2 event buffer. Of course, DRI2 direct rendering doesn't exist yet. Finally, this commit bumps the DRI interface version again, accounting for the change in the DRI_TEX_BUFFER extension and the change in commit 0bba0e5be7a4a7275dad1edc34bdcc134ea1f424 to pass in the event buffer head index on drawable creation.
* DRI2: Add event buffer head as an argument to driCreateNewDrawable().Kristian Høgsberg2008-03-091-0/+1
| | | | The DRI driver needs to know where in the buffer to start reading.
* [dri2] Add tail pointer to reemitDrawableInfo callback.Kristian Høgsberg2008-03-031-1/+2
| | | | | | | | When the DRI doesn't parse the event buffer for a while, the X server may overwrite data that the driver didn't get a chance to look at. The reemitDrawableInfo callback requests that the X server reemit all info for the specified drawable. To make use of this, the drive needs to know the new tail pointer so it know where to start reading from.
* Use __DRIextension mechanism providing loader functionality to the driver.Kristian Høgsberg2008-02-291-22/+60
| | | | | | | Instead of passing in a fixed struct, the loader now passes in a list of __DRIextension structs, to advertise the functionality it can provide to the driver. Each extension is individually versioned and can be extended or phased out as the interface develops.
* Reduce the versioning madness required to create a DRI2 screen.Kristian Høgsberg2008-02-291-5/+2
| | | | | | | | | | | | | | | | | | Right now the DRI2 screen constructor takes 3 different versions: DRI, DDX and DRM. This is mostly useless, though: DRI: The DRI driver doesn't actually care about the DRI protocol, it only talks to the loader, which in turn speaks DRI protocol. Thus, the DRI protocol version is of not interest to the DRI driver, but it needs to know what functionality the loader provides. At this point that's reflected in the __DRIinterfaceMethods struct and the internal_version integer. DDX: The DDX version number is essentially used to track extensions to the SAREA. With DRI2 the SAREA consists of a number of versioned, self-describing blocks, so the DDX version is no longer interesting. DRM: We have the fd, lets just ask the kernel ourselves.
* Convert crlf->lf line endings.José Fonseca2008-02-281-79/+79
| | | | | | Windows/DOS users should enable core.autocrlf from now on: git config --global core.autocrlf true
* Remove GetMSC DriverAPI function.Kristian Høgsberg2008-02-251-13/+2
| | | | | | | | | | | The DriverAPI is internal to the DRI drivers and GetDrawableMSC obsoletes GetMSC. Also, since the DRI driver interface has not yet been released, just drop the getMSC function from the DRI interface instead using the ABI preserving version mechanism. Finally, using void pointer privates in the DRI interface is not allowed, always pass the actual types around (__DRIdrawable in this case) to enhance type safety and readability of the code.
* Add TTM buffer object based texture from pixmap implementation.Kristian Høgsberg2008-02-141-0/+20
| | | | Currently only implemented for intel hw.
* Add new DRI2 infrastructure.Kristian Høgsberg2008-02-142-6/+163
|
* Fix GLX build of xserver master branch.Michel Dänzer2007-11-051-0/+5
| | | | The internal CreatePixmap API has been extended.
* Refactor and fix core vblank supportJesse Barnes2007-10-291-1/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Consolidate support for synchronizing to and retrieving vblank counters. Also fix the core vblank code to return monotonic MSC counters, which are required by some GLX extensions. Adding support for multiple pipes to a low level driver is fairly easy, the Intel 965 driver provides simple example code (see intel_buffers.c:intelWindowMoved()). The new code bumps the media stream counter extension version to 2 and adds a new getDrawableMSC callback. This callback takes a drawablePrivate pointer, which is used to calculate the MSC value seen by clients based on the actual vblank counter(s) returned from the kernel. The new drawable private fields are as follows: - vblSeq - used for tracking vblank counts for buffer swapping - vblFlags - flags (e.g. current pipe), updated by low level driver - msc_base - MSC counter from the last time the current pipe changed - vblank_base - kernel DRM vblank counter from the last time the pipe changed Using the above variables, the core vblank code (in vblank.c) can calculate a monotonic MSC value. The low level DRI drivers are responsible for updating the current pipe (by setting VBLANK_FLAG_SECONDARY for example in vblFlags) along with msc_base and vblank_base whenever the pipe associated with a given drawable changes (again, see intelWindowMoved for an example of this). Drivers should fill in the GetDrawableMSC DriverAPIRec field to point to driDrawableGetMSC32 and add code for pipe switching as outlined above to fully support the new scheme.
* Add GL_CORE_WINDOWS define to glcore.hGeorge Sapountzis2007-10-141-0/+1
| | | | | | | | | | | | This is for consistency with glproto. The GL_CORE defines should probably be dropped. ---- Author: Alexander Gottwald <[email protected]> Date: Mon Jun 21 13:35:05 2004 +0000 Bug 782: Merge native OpenGL for Windows from CYGWIN branch
* Add a version field to __DRIextension.Kristian Høgsberg2007-10-111-0/+23
|
* Move new texOffset extension to the new extension mechanism.Kristian Høgsberg2007-10-111-12/+17
|
* Convert a left-over private void * to __DRIcontext *.Kristian Høgsberg2007-10-111-1/+1
|
* Remove now unused getProcAddress from DRIinterfaceMethods.Kristian Høgsberg2007-10-111-38/+0
|
* Add a DRI_ReadDrawable marker extension to signal read drawable capability.Kristian Høgsberg2007-10-111-0/+5
|
* Move media stream counter entry points to new extension.Kristian Høgsberg2007-10-111-49/+27
|
* Move GLX_MESA_swap_frame_usage DRI entry points to the new mechanism.Kristian Høgsberg2007-10-111-16/+25
|
* Move GLX_MESA_allocate_memory related functions to new extension mechanism.Kristian Høgsberg2007-10-111-16/+18
|
* Move swap_interval to new extension mechanism.Kristian Høgsberg2007-10-101-8/+11
|
* Move the copySubBuffer extension over to the new mechanism.Kristian Høgsberg2007-10-101-8/+10
|
* Implement new screen extension API.Kristian Høgsberg2007-10-101-0/+20
| | | | | | | | | | | | This new API lets the loader examine DRI level extensions provided by the driver in a forward compatible manner. Much of the churn in the DRI interface is adding support for new extensions or removing old, unused extensions. This new extension mechanism lets the loader query the extensions provided by the driver and implement the extensions it knows about. Deprecating extensions is done by not exporting that extension in the list, which doesn't require keeping old function pointers around to preserve ABI.
* Stop passing in unused fbconfigs to createNewScreen.Kristian Høgsberg2007-10-101-1/+0
|
* Convert all DRI entrypoints to take pointers to __DRI* types.Kristian Høgsberg2007-10-101-20/+20
| | | | | | | | | | The entrypoints take a mix of __DRIscreen * and void * (screen private) arguments (similarly for contexts and drawables). This patch does away with passing the private void pointer and always only passes the fully typed __DRIscreen pointer and always as the first argument. This makes the interface more consistent and increases type safety, and catches a bug where we would pass a screen private to DRIdrawable::getSBC.
* Remove screenConfigs from __DRIscreen.Kristian Høgsberg2007-10-101-11/+2
| | | | | | | | | | | | 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 mostly unused __DRIid typedef.Kristian Høgsberg2007-10-101-1/+0
|
* Drop createContext and destroyContext from DRIinterfaceMethods.Kristian Høgsberg2007-10-101-12/+2
| | | | | | | | | | As for createDrawable and destroyDrawable, these functions immediately upon entry to driCreateNewContext and immediately before exit from driDestroyContext. Instead of passing function pointers back and forth just obtain the drm_context_t prior to calling DRIscreen::createNewContext and pass it as a parameter. This change also lets us keep the DRI context XID in the libGL loader only.
* Drop createDrawable and destroyDrawable fron DRIinterfaceMethods.Kristian Høgsberg2007-10-101-13/+3
| | | | | | | | | | | | All the DRI driver did was call the createDrawable callback immediately upon entry to DRIscreen::createNewDrawable to get the drm_drawable_t. We can just call that before calling into the DRI driver and pass the returned drm_drawable_t as an argument to the DRI entry point. Likewise for destroyDrawable. Also, DRIdrawablePrivate::draw isn't used anywhere, and since the driver no longer needs the XID of the drawable we can now drop that.
* Drop __DRInativeDisplay and pass in __DRIscreen pointers instead.Kristian Høgsberg2007-10-101-42/+33
| | | | | | | | | | | | | 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.
* Add macros to generate CreateNewScreen entrypoint.Kristian Høgsberg2007-10-051-1/+19
|
* Remove XIDs from DRI interface (see #5714).Kristian Høgsberg2007-10-051-38/+17
|
* Add glut_fcb.c to the build and update to fix warnings (see bug 12405)Brian2007-09-121-2/+2
|
* Unbreak Linux builds with -fvisibility=hidden.Adam Jackson2007-08-231-16/+11
|
* more Mingw32 fixesZhang2007-07-273-9/+2
|
* Fix a number of MINGW32 issuesZhang2007-07-213-38/+47
|
* regeneratedBrian2007-06-291-0/+93
|
* a variety of fixes for MingWzhang2007-06-282-3/+18
|
* add glxtokens.h to xmesa_xf86.h as discussed on mailing listDave Airlie2007-05-261-0/+1
|
* Add interfaces for overriding texture images with driver specific 'offsets'.Michel Dänzer2007-05-221-0/+12
| | | | | To be used by AIGLX for GLX_EXT_texture_from_pixmap without several additional data copies.
* Fix xserver build after recent XMesa changes.Michel Dänzer2007-05-223-3/+31
| | | | Only build tested.
* Disable (at least for now) PFNGLFRAMEBUFFERTEXTURELAYEREXTPROC typedef.Brian2007-05-191-0/+5
| | | | | | If an app (like progs/samples/blendxor.c) includes both gl.h and glext.h this typedef will get hit in both headers, causing an error. Possibly work around by bringing GL_NV_geometry_program4 items into gl.h.
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-29 18:06:22 +0000