aboutsummaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Move make install logic for libGL back into src/mesa/Makefile.Kristian Høgsberg2008-03-103-17/+24
| | | | | | | | | This makes make install work again for non-glx libGL implementations. The make install logic is split into three sub-targets: install-libgl, install-osmesa, install-drivers. The install target in src/glx/x11 is then implemented using the src/mesa make install-libgl rule. Thanks to Dan Nicholson for pointing out the breakage.
* Only try to call DRI function if DRI got initialized properly.Kristian Høgsberg2008-03-102-4/+7
|
* Darwin: Config/source fixes to now build glxdemo apps and OSMesaJeremy Huddleston2008-03-106-44/+22
| | | | | Also added darwin-fat-32bit darwin-fat-all configs and deleted old darwin-x86ppc config (cherry picked from commit 7120c0089d663a2b7e7b0c97da38f9bc233fbdd7)
* autoconf: Add autogen.sh from Xorg for easier setup from gitDan Nicholson2008-03-102-3/+22
| | | | | | | The defacto method to rebuild the autotools and run the generated configure is an autogen.sh script. It is much more discoverable than the custom `make configure' used here. The Makefile targets are still useful for creating tarballs, though. This autogen.sh is copied from Xorg.
* Ignore more demo programsDan Nicholson2008-03-102-1/+3
|
* remove extra #include of assert.h (bug 14932)Brian2008-03-101-1/+0
|
* fix parsing of state.texenv.color (bug 14931)Brian2008-03-102-2/+4
|
* dri: fix function call to add new parameter.Dave Airlie2008-03-101-0/+1
| | | | This may not be correct but it should get the build going.
* DRI2: Make setTexBuffer take a __DRIdrawable instead of a BO handle.Kristian Høgsberg2008-03-093-25/+21
| | | | | | | | | | | | | | | | | 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: Drop DriverAPI.UpdateBuffer.Kristian Høgsberg2008-03-093-27/+23
| | | | | | | __dri2ParseEvents() would determine the kind of event, but then call UpdateBuffer() in either case, and UpdateBuffer() would then have to figure that out again to dispatch to HandleBufferAttach() or HandleDrawableConfig(). Pretty pointless.
* DRI2: Pass the context instead of the screen to __dri2ParseEvents().Kristian Høgsberg2008-03-093-9/+6
| | | | | | Makes a lot more sense, since the screen is always implicit in the DRI drawable, but it may not be possible to track down a context from just a drawable.
* DRI2: Add event buffer head as an argument to driCreateNewDrawable().Kristian Høgsberg2008-03-092-2/+4
| | | | The DRI driver needs to know where in the buffer to start reading.
* fix botched test for clearing color buffers (should fix depth peeling ↵Brian2008-03-091-3/+4
| | | | regression)
* Set normalized flag for GLubyte arrays in _mesa_VertexAttribPointerNV()Markus Amsler2008-03-091-1/+2
|
* init vertex weight attrib to (1,0,0,0)Markus Amsler2008-03-091-1/+1
|
* fix __builtin_expect() definition test for IBM XLC (sf bug 1909832)Brian2008-03-091-1/+1
|
* Properly revert the libGL loader path breakage.Kristian Høgsberg2008-03-091-0/+1
|
* libGL: Fall back to DEFAULT_DRIVER_DIR properly.Kristian Høgsberg2008-03-091-1/+2
| | | | | | | | After commit 6fd82f6fbd208dc7b1839ea408a5fb28589ee622, we would overwrite the libPath default value with NULL if libGL was running non-setuid and none of the env vars were set. Thanks to Magnus Kessler <[email protected]> for spotting it.
* replace // comment with /* */ (bug 14916)Brian2008-03-091-1/+1
|
* added info about checking out gallium-0.1 for cell codeBrian2008-03-091-0/+6
|
* Use _X_HIDDEN to hide a bunch of leaked symbols.Kristian Høgsberg2008-03-085-37/+43
|
* Move DRI context functions into dri_glx.c.Kristian Høgsberg2008-03-087-129/+153
| | | | Also drop isDirect flag; if gc->driContext is non-NULL, it's direct.
* Move DRI drawable creation into dri_glx.c.Kristian Høgsberg2008-03-084-56/+68
|
* Introduce __GLXDRIscreen so we can start moving function pointers in there.Kristian Høgsberg2008-03-085-48/+58
| | | | | Temporarily rename the __DRIscreen member to __driScreen. Eventually, we'll move that into __GLXDRIscreen and only access it in dri_glx.c.
* Move DRI specific parts of CreateContext into dri_glx.c.Kristian Høgsberg2008-03-083-29/+43
|
* Convert driCreateScreen and driDestroyScreen to function pointers.Kristian Høgsberg2008-03-083-19/+23
| | | | | We avoid leaking the symbols and will be able to replace them with DRI2 implementation later on.
* Abstract __DRIdisplayPrivateRec away in dri_glx.c.Kristian Høgsberg2008-03-085-101/+37
| | | | | | | | This patch moves __DRIdisplayPrivateRec definition into dri_glx.c and let's dri_glx.c allocate the __DRIdisplay struct pointer to from __GLXdisplayPrivate. A small step towards moving more of the dri functionality into dri_glx.c.
* Make __glXCloseDisplay static instead of prototyping it to avoid warning.Kristian Høgsberg2008-03-081-9/+1
|
* Move libGL install target to the libGL Makefile.Kristian Høgsberg2008-03-083-17/+16
|
* Simplify LIBGL_DRIVERS_PATH walking.Kristian Høgsberg2008-03-081-76/+19
|
* Simplify dri loading code by eliminating dlopen "cache".Kristian Høgsberg2008-03-084-185/+46
| | | | | | | No need to jump through hoops to track __DRIdrivers and avoid dlopening the same .so more than twice, dlopen() does this internally. Besides, we were already bypassing this and dlopening drivers for each screen, whether or not they were already dlopened.
* libGL: Consolidate DRI initialization in dri_glx.cKristian Høgsberg2008-03-083-406/+411
| | | | Move a lot of code over from glx_ext.c.
* autoconf: Print GCC include path directly and be more robust using itDan Nicholson2008-03-071-4/+5
| | | | | | | | Rather than constructing the GCC include path from `-print-search-dirs', we can get the path directly from `-print-file-name=include'. This is used in the Linux kernel build, for example. If no output is returned from the command, then we don't append a -I path the the makedepend options.
* [intel] Only enable GL_EXT_texture_sRGB on i965.Kristian Høgsberg2008-03-071-1/+1
| | | | Fixes #14799.
* [i965] fix fd.o bug #11471 and #11478Zou Nan hai2008-03-073-8/+23
| | | | | 1. Follow EXT_texture_rectangle with YCbCr texture 2. swap UV component for MESA_FORMAT_YCBCR
* i965: use RGB565 to render a bitmap if Depth is 16Xiang, Haihao2008-03-071-10/+10
|
* i965: Fix double free issue to pass glean/maskedClear testXiang, Haihao2008-03-061-0/+1
|
* i965:fix segfault issue when clearing the window whichXiang, Haihao2008-03-061-1/+2
| | | | | is created with mode GLUT_SINGLE|GLUT_RGB|GLUT_DEPTH. This issue is introduced by 20b8bff49cba3e8246e29004c5ff38f231d589ff
* [intel] Add a driconf option to cache freed buffer objects for reuse.Eric Anholt2008-03-055-15/+209
| | | | | | | | | This is defaulted off as it has potentially large memory costs for a modest performance gain. Ideally we will improve DRM performance to the point where this optimization is not worth the memory cost in any case, or find some middle ground in caching only limited numbers of certain buffers. For now, this provides a modest 4% improvement in openarena on GM965 and 10% in openarena on GM945.
* r300: replace some hard coded mask by define in stencil areaChristoph Brill2008-03-041-6/+6
|
* r300: Fix some issues with masks in stencil buffer areaChristoph Brill2008-03-042-6/+7
|
* [dri2] Add tail pointer to reemitDrawableInfo callback.Kristian Høgsberg2008-03-032-2/+3
| | | | | | | | 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.
* [dri2] Optimize event parsing to skip obsolete events.Kristian Høgsberg2008-03-031-40/+84
| | | | | | This also fixes the problem where the X server does multiple resizes before the DRI driver gets the events. The obsolete buffer attach events then reference already destroyed buffer objects.
* [intel] Silence unused variable warning when compiling for i965.Kristian Høgsberg2008-03-031-0/+3
|
* nouveau: compilation fixesPatrice Mandin2008-03-021-2/+2
|
* state.depth.range alpha value should be 1, not 0 (bug #14733)Roland Scheidegger2008-03-011-1/+1
|
* Update libGL DRI loader to latest DRI interface changes.Kristian Høgsberg2008-02-293-58/+22
|
* glxgears: oops, remove accidental commit of glFinish() hack.Kristian Høgsberg2008-02-291-1/+0
|
* Use __DRIextension mechanism providing loader functionality to the driver.Kristian Høgsberg2008-02-2928-179/+207
| | | | | | | 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-294-31/+25
| | | | | | | | | | | | | | | | | | 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.
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-02 12:07:13 +0000