summaryrefslogtreecommitdiffstats
path: root/src/mesa
Commit message (Collapse)AuthorAgeFilesLines
* mesa: avoid to unlock an unlocked array in _mesa_PopClientAttribXiang, Haihao2008-03-171-1/+1
|
* mesa: Follow GL spec to draw DEPTH_COMPONENT pixels whenXiang, Haihao2008-03-171-2/+1
| | | | there's no depth buffer. Fix bug #11580
* [i965] fix wpos height 1 pixel higherZou Nan hai2008-03-172-2/+2
|
* init tmpNode to zerosBrian2008-03-141-0/+1
|
* mesa: fix emit_clamp() so that we don't use an output register as temporaryBrian2008-03-141-3/+12
| | | | | | IR_CLAMP is decomposed into OPCODE_MIN+OPCODE_MAX. Allocate a temporary register for the intermediate value so we don't inadvertantly use an output register (which are write-only on some GPUs).
* intel: fix abort issue with shadowtex demo when useXiang, Haihao2008-03-143-24/+45
| | | | DEPTH_STENCIL texture. (bug#14952).
* fix state.lightprod ambient/specular w value (bug #14983)Roland Scheidegger2008-03-131-2/+2
|
* [i965] multiple rendering target supportZou Nan hai2008-03-1315-98/+135
|
* Move make install logic for libGL back into src/mesa/Makefile.Kristian Høgsberg2008-03-102-2/+33
| | | | | | | | | 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.
* fix parsing of state.texenv.color (bug 14931)Brian2008-03-102-2/+4
|
* DRI2: Make setTexBuffer take a __DRIdrawable instead of a BO handle.Kristian Høgsberg2008-03-092-18/+16
| | | | | | | | | | | | | | | | | 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-091-2/+3
| | | | 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
|
* replace // comment with /* */ (bug 14916)Brian2008-03-091-1/+1
|
* Move DRI context functions into dri_glx.c.Kristian Høgsberg2008-03-081-1/+1
| | | | Also drop isDirect flag; if gc->driContext is non-NULL, it's direct.
* Move libGL install target to the libGL Makefile.Kristian Høgsberg2008-03-082-26/+1
|
* [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-031-1/+1
| | | | | | | | 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
|
* Use __DRIextension mechanism providing loader functionality to the driver.Kristian Høgsberg2008-02-2926-157/+146
| | | | | | | 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-293-26/+23
| | | | | | | | | | | | | | | | | | 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.
* intel: Set the lock flag early to avoid deadlock.Kristian Høgsberg2008-02-291-0/+1
| | | | Another regression from the intel_context.c merge.
* i965: use _Current pointer instead of Current pointer.Xiang, Haihao2008-02-294-24/+7
| | | | fix double free issue(bug#14710). It also corrects glsl/bitmap demo behavior.
* [965] Fix conditional sequencing to allow the frame_buffer_texobj case.Eric Anholt2008-02-281-8/+6
| | | | | Previously the frame_buffer_texobj case would have been bound as a normal texture, at best resulting in no surface data being associated with it.
* [intel] Bug #14575: Unmap buffers when deleting/dataing as required.Eric Anholt2008-02-281-0/+16
| | | | | Otherwise, we would assertion error when doing the final unreference of the buffer with an outstanding map (catching the memory leak).
* r300: R5xx and R3xx use different registers for RS_IP and RS_INSTChristoph Brill2008-02-284-97/+157
| | | | | These changes are taken from the xf86-video-ati driver. They update the header file accordingly and also remove some UNKOWN variables.
* [965] Bug #9151: make fragment.position return window coords not screen coords.Eric Anholt2008-02-284-22/+54
|
* [965] Fix serious copy'n'paste failure in brw state dumping.Eric Anholt2008-02-281-3/+3
|
* mesa: separate shader program object from shader object.Xiang, Haihao2008-02-283-13/+21
| | | | | | | | | Currently a callback delete_shader_cb is used for deleting shader and shader program objects. Mesa detaches all attached shaders in _mesa_free_shader_program_data when deleting shader program objects. However it is likely that these shaders have been freed in _mesa_free_shader, which will result in unexpected behaviour. This fix uses a single callback for shader program objects and deletes shader program objects before shader objects.
* [intel] fix compressed image heightZou Nan hai2008-02-281-1/+1
|
* Convert crlf->lf line endings.José Fonseca2008-02-2819-7025/+7025
| | | | | | Windows/DOS users should enable core.autocrlf from now on: git config --global core.autocrlf true
* r300: properly handle GL_POINT in glPolygonModeChristoph Brill2008-02-271-5/+10
| | | | | | Until now the polygon mode was completely turned of when you used GL_POINT. For me it looked buggy to completely disable the polygon mode for FrontMode and BackMode if any of these was GL_POINT.
* intel: Always use intelInitExtensions() for initializing extensions.Kristian Høgsberg2008-02-274-35/+17
|
* r300: add artificial output to match fragment program inputMarkus Amsler2008-02-272-7/+28
|
* mesa: set input read only on successMarkus Amsler2008-02-271-2/+2
|