aboutsummaryrefslogtreecommitdiffstats
path: root/src/mesa/drivers/dri/intel
Commit message (Collapse)AuthorAgeFilesLines
* intel: use new _mesa_meta_copy_pixels() functionBrian Paul2009-08-101-165/+2
| | | | glCopyPixels() no longer hits a software fallback when zooming, blending, etc.
* intel: add missing \n to fprintf()Brian Paul2009-08-101-1/+1
|
* intel: use new _mesa_meta_blit_framebuffer() functionBrian Paul2009-08-102-69/+7
| | | | | The previous version of framebuffer blit was a quick hack. The new meta version works pretty well.
* Revert "i965: Disable texture tiling by default."Eric Anholt2009-08-071-1/+5
| | | | | | | This reverts commit b8e638d4895d2d342306bb6443a455f73903ce20. Now that the known hangs and misrendering issues are fixed, I'm ready to start encouraging it by default again.
* intel: Align region height as required for tiled regions.Eric Anholt2009-08-071-0/+5
| | | | | | | Otherwise, we would address beyond the end of our buffers. Fixes reliable GPU segfault with texture_tiling=true and oglconform shadow.c. Bug #22406.
* intel: Add some more safety asserts in the blit code.Eric Anholt2009-08-071-0/+3
|
* intel: minor context commentsBrian Paul2009-08-071-1/+5
|
* intel: move blit call out of assert()Brian Paul2009-08-071-7/+9
|
* intel: fix typo: s/softare/software/Brian Paul2009-08-071-2/+2
|
* Merge branch 'mesa_7_5_branch'Brian Paul2009-08-051-0/+5
|\ | | | | | | | | | | Conflicts: src/mesa/main/state.c
| * intel: Fix inverted test for disabling flushing of front buffer output.Brian Paul2009-08-041-1/+1
| | | | | | | | | | | | | | | | | | | | The comment disagreed with the code, and nicely drew my eyes to what was going wrong. Bug #21774 (blender) Bug #21788 (readpix) (cherry picked from master, commit fd65418f600874b05f902b622078b40bc1abb24a)
| * intel: Wait on the last swapbuffers to complete before queuing a new one.Brian Paul2009-08-043-0/+28
| | | | | | | | | | | | | | | | | | | | | | | | | | This fixes jerkiness in doom3 and other apps since the kernel change to throttle less absurdly, which led to a thundering herd of frames. Because this is a rather minimal fix, there is at least one downside: If the whole scene completes in one batchbuffer, we'll end up stalling the GPU. Thanks to Michel Dänzer for suggesting using glFlush to signal frame end instead of going to all the effort of adding a new DRI2 extension. (cherry picked from master, commit 0828579a658af01a64b5e699175dc9bbbedcd685)
* | intel: implement intelCompressedTexSubImage2DRoland Scheidegger2009-08-051-21/+44
| | | | | | | | | | similar to the radeon code. passes tests/texcompsub
* | intel: Add support for EXT_provoking_vertex.Eric Anholt2009-08-041-0/+2
| |
* | intel: Fix inverted test for disabling flushing of front buffer output.Eric Anholt2009-08-031-1/+1
| | | | | | | | | | | | | | | | The comment disagreed with the code, and nicely drew my eyes to what was going wrong. Bug #21774 (blender) Bug #21788 (readpix)
* | intel: Wait on the last swapbuffers to complete before queuing a new one.Eric Anholt2009-08-033-0/+28
| | | | | | | | | | | | | | | | | | | | | | This fixes jerkiness in doom3 and other apps since the kernel change to throttle less absurdly, which led to a thundering herd of frames. Because this is a rather minimal fix, there is at least one downside: If the whole scene completes in one batchbuffer, we'll end up stalling the GPU. Thanks to Michel Dänzer for suggesting using glFlush to signal frame end instead of going to all the effort of adding a new DRI2 extension.
* | i915: Add support for EXT_stencil_two_side and ATI_separate_stencil.Eric Anholt2009-07-291-0/+2
| | | | | | | | Passes tests/stencil_twoside and glean/stencil2.
* | i915: Add ARB_point_sprite since we already expose NV_point_sprite.Eric Anholt2009-07-291-0/+1
| | | | | | | | It's all fallbacks anyway due to the DD_POINT_ATTEN fallback.
* | Merge branch 'mesa_7_5_branch'Brian Paul2009-07-281-3/+3
|\| | | | | | | | | | | | | | | | | Conflicts: Makefile configs/default docs/relnotes.html src/mesa/main/version.h
| * intel: Fix leak of DRI option info due to using the wrong free routine.Brian Paul2009-07-271-1/+1
| | | | | | | | (cherry picked from commit 6d66f23c50ebe8f973757b6fd1b81c9b7920c447)
| * intel: Clean up leak of driver context structure on context destroy.Brian Paul2009-07-271-0/+3
| | | | | | | | (cherry picked from commit ddef7dc87b2001fbe117ee5f24a0c645ee95a03c)
| * intel: Use _mesa_warning() to report GEM warningsBrian Paul2009-07-271-3/+3
| |
| * intel: Fall back on glBitmap with fog enabled.Eric Anholt2009-07-201-0/+6
| | | | | | | | | | | | | | | | We would have to build the program with the appropriate fog mode, and also supply the fog coordinate if appropriate. Bug #19413. (cherry picked from commit 8ae02a3919bf31bd33f86208472e100eedb58497)
* | intel/radeon: add common metaops code.Dave Airlie2009-07-158-570/+32
| | | | | | | | | | Move all the metaops to a dri_metaops file and port radeon/intel to use the new common meta ops code.
* | intel: Fix ClearDepth to not be affected by DepthRange.Eric Anholt2009-07-141-1/+7
| | | | | | | | Fixes new piglit depthrange-clear.c test.
* | intel: Set DepthRange in the metaops using RasterPos[2].Eric Anholt2009-07-142-1/+9
| | | | | | | | | | | | | | RasterPos[2] is already sent through the window transform, which includes DepthRange handling. So make DepthRange for the metaops a noop. Fixes a failure in oglconform depthrange.c
* | intel: Flag _NEW_ARRAY state when doing array object binding in clears.Eric Anholt2009-07-141-0/+8
| | | | | | | | This is just following bind_vertex_array()'s behavior.
* | intel: Partially fix fallback detection for glCopyTexSubImage.Eric Anholt2009-07-131-6/+10
| | | | | | | | | | | | | | | | | | Really, we should be checking that the MesaTexFormat for the read buffer and the texture match, but the previous code wasn't even doing that, so matching the cpp should be an improvement (and potentially fix some hangs!). The previous code also rejected GL_RGB even though blitting the alpha channel to the ignored channel of an x8r8g8b8 texture should be fine, which tripped up compiz's blur plugin.
* | Merge branch 'mesa_7_5_branch'Brian Paul2009-07-131-1/+1
|\|
| * intel: Bump driver data, add RC3 tagintel_2009q2_rc3Ian Romanick2009-07-121-1/+1
| |
* | i965: add support for new chipsetsXiang, Haihao2009-07-136-19/+61
| | | | | | | | | | | | | | | | | | | | 1. new PCI ids 2. fix some 3D commands on new chipset 3. fix send instruction on new chipset 4. new VUE vertex header 5. ff_sync message (added by Zou Nan Hai <[email protected]>) 6. the offset in JMPI is in unit of 64bits on new chipset 7. new cube map layout
* | intel: Fix flipped Y for glDrawPixels(GL_STENCIL_INDEX) to window system.Eric Anholt2009-07-071-5/+17
| | | | | | | | | | Even after fixing bugs in this code, it doesn't make me feel any cleaner. Fixes piglit stencil-drawpixels.
* | intel: Fall back on glCopyPixels(GL_DEPTH) or GL_STENCIL.Eric Anholt2009-07-071-0/+6
| |
* | Merge branch 'mesa_7_5_branch'Jakob Bornecrantz2009-07-031-0/+1
|\| | | | | | | | | | | Conflicts: src/mesa/main/dlist.c src/mesa/vbo/vbo_save_api.c
| * intel: Also update stencil bits in intel_update_wrapper().Michel Dänzer2009-07-031-0/+1
| | | | | | | | | | Fixes assertion failure when binding depth/stencil texture to FBO stencil attachment.
| * i915: Fix assertion failure on remapping a non-BO-backed VBO.Eric Anholt2009-06-301-1/+4
| | | | | | | | | | | | Failure to set the obj->Pointer back to null tripped up the assertion. Bug #22428. (cherry picked from commit 57a06d3a48c9af1067ec05e3ad96c58f4b9b99be)
* | intel: Fall back on glBitmap with fog enabled.Eric Anholt2009-07-021-0/+6
| | | | | | | | | | | | | | We would have to build the program with the appropriate fog mode, and also supply the fog coordinate if appropriate. Bug #19413.
* | intel: Flush when mapping buffer objects so writes don't get reordered.Eric Anholt2009-07-022-0/+5
| | | | | | | | | | While GEM covers this for execution it knows about, it doesn't know about the batchbuffer we're preparing. Fixes piglit vbo-map-remap.c testcase.
* | intel: Fix leak of DRI option info due to using the wrong free routine.Eric Anholt2009-07-021-1/+1
| |
* | intel: Clean up leak of driver context structure on context destroy.Eric Anholt2009-07-021-1/+2
| |
* | intel: Init num_fences to clean up valgrind warning.Eric Anholt2009-07-021-1/+1
| | | | | | | | | | Valgrind doesn't know that a successful getparam sets the target of the pointer, so just set the value beforehand.
* | intel: Avoid pointer arithmetic on void *.Eric Anholt2009-06-301-1/+1
| | | | | | | | Bug #22000.
* | i915: Fix assertion failure on remapping a non-BO-backed VBO.Eric Anholt2009-06-301-1/+4
| | | | | | | | | | Failure to set the obj->Pointer back to null tripped up the assertion. Bug #22428.
* | intel: Enable EXT_gpu_program_parameters.Eric Anholt2009-06-291-0/+2
| | | | | | | | | | There doesn't appear to be any driver impact for enabling this, and tests/prog_parameter passes.
* | Merge branch 'mesa_7_5_branch'Brian Paul2009-06-291-1/+1
|\|
| * intel: added null ptr checkBrian Paul2009-06-291-1/+1
| | | | | | | | This fixes a segfault seen with piglit's fdo20701 test.
* | Revert "intel: Remove unneded pthread mutex in LOCK_HARDWARE."Eric Anholt2009-06-291-1/+8
| | | | | | | | | | | | | | | | | | | | | | This reverts commit de447afff26706e3bf8bdcd5cfb8b1daf49b4b21 but puts the lock under DRI1-only. From keithw: > It's there because the DRI1 code doesn't actually achieve the mutexing > which it looks as if it should. For multi-threaded applications it was > always possible to get two threads inside locked regions -- I have no > idea how, but it certainly was and presumably still is possible.
* | intel: Move note_unlock() implementation to the one place it's needed.Eric Anholt2009-06-292-2/+0
| |
* | intel: Remove unneded pthread mutex in LOCK_HARDWARE.Eric Anholt2009-06-291-6/+0
| | | | | | | | | | | | | | | | | | | | | | | | This would cause LOCK_HARDWARE to mutex all contexts in this process on both DRI1 and DRI2. On DRI1, LOCK_HARDWARE already does it for all processes on the system. On DRI2, LOCK_HARDWARE doesn't, but there shouldn't be any state outside the context that needs any additional protection. Notably, the bufmgr is protected by its own mutex and not LOCK_HARDWARE. This code was originally introduced with the i915tex code dump, so it's not clear what it was there for.
* | intel: Make LOCK_HARDWARE recursive to avoid hand-rolling recursiveness.Eric Anholt2009-06-294-42/+17
| |
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-14 08:48:04 +0000