summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* Merge branch 'mesa_7_5_branch'Jakob Bornecrantz2009-07-0414-179/+378
|\
| * gallium: Fixes for clobbering stencil values in combined depth/stencil textures.Michel Dänzer2009-07-073-11/+64
| | | | | | | | | | Also fix one case where a 32 bit depth value was incorrectly converted to a combined depth/stencil value.
| * GLX/DRI1: Mark GLX visuals with depth != screen depth non-conformant.Michel Dänzer2009-07-071-0/+23
| | | | | | | | | | Such visuals are subject to automatic compositing in the X server, so DRI1 can't render to them properly.
| * gallium: Only set FRONT_STATUS_COPY_OF_BACK if there is a back buffer.Michel Dänzer2009-07-071-1/+2
| | | | | | | | Fixes potential crash when SwapBuffers is called but there's no back buffer.
| * gallium: more fog extraction fixesZack Rusin2009-07-063-25/+39
| | | | | | | | | | fix the cases when fog coord/front face/point coord are used in the same shader.
| * demos: Fix vsync checking in glxgearsIan Romanick2009-07-061-19/+16
| | | | | | | | | | | | | | | | | | | | Of course glXGetVideoSyncSGI doesn't return the swap interval. The feature only exists in the Mesa extension... which is the whole reason I created the Mesa extension! Note that the Mesa extension allows drivers to default to a swap interval of 0. If the Mesa extension exists, use its value. Only consider the SGI extension when the Mesa extension is not available. Fixes bug #22604.
| * wgl: Make the stw_framebuffer destructions threadsafe.José Fonseca2009-07-065-82/+186
| | | | | | | | | | | | | | Ensure no other thread is accessing a framebuffer when it is being destroyed by acquiring both the global and per-framebuffer mutexes. Normal access only needs the global lock to walk the linked list and acquire the per-framebuffer mutex.
| * wgl: Check for multiple threads before GET_CURRENT_CONTEXT.José Fonseca2009-07-061-2/+8
| | | | | | | | | | Fixes wglthreads -- the 2nd thread MakeCurrent call was trying to flush the first thread context while still in use.
| * wgl: Listen to WM_WINDOWPOSCHANGED instead of WM_SIZE messages.José Fonseca2009-07-061-44/+45
| | | | | | | | | | | | | | | | | | | | According to http://blogs.msdn.com/oldnewthing/archive/2008/01/15/7113860.aspx WM_SIZE is generated from WM_WINDOWPOSCHANGED by DefWindowProc so it can be masked out by the application. Also there were some weird bogus WM_SIZE 0x0 messages when starting sharedtex_mt which we don't get like this.
| * i965: fix fetching constants from constant buffer in glsl pathRoland Scheidegger2009-07-044-17/+16
| | | | | | | | | | | | | | | | | | | | | | | | the driver used to overwrite grf0 then use implicit move by send instruction to move contents of grf0 to mrf1. However, we must not overwrite grf0 since it's still used later for fb write. Instead, do the move directly do mrf1 (we could use implicit move from another grf reg to mrf1 but since we need a mov to encode the data anyway it doesn't seem to make sense). I think the dp_READ/WRITE_16 functions may suffer from the same issue. While here also remove unnecessary msg_reg_nr parameter from the dataport functions since always message register 1 is used.
| * i965: Remove bad constant buffer constant-reg-already-loaded optimization.Eric Anholt2009-07-041-13/+11
| | | | | | | | | | | | | | Thanks to branching, the state of c->current_const[i].index at the point of emitting constant loads for this instruction may not match the actual constant currently loaded in the reg at runtime. Fixes a regression in my GLSL program for idr's class since b58b3a786aa38dcc9d72144c2cc691151e46e3d5.
* | progs/tests: Tests more views in mipmap_comp_testsJakob Bornecrantz2009-07-041-1/+4
| |
* | Merge commit 'origin/openvg-1.0'Zack Rusin2009-07-0687-0/+25258
|\ \
| * | vg: remove a silly demo and add a bit better oneZack Rusin2009-05-014-197/+544
| | |
| * | docs: asst updates to openvg.htmlBrian Paul2009-05-011-7/+27
| | |
| * | OpenVG 1.0 State TrackerZack Rusin2009-05-0186-0/+24891
| | | | | | | | | | | | Import of the OpenVG 1.0 state tracker for Gallium.
* | | gallium: rearrange some members to avoid memory holes/paddingZack Rusin2009-07-062-8/+8
| | | | | | | | | | | | plus it saves us a cacheline in the cso
* | | pipebuffer: handle possible null pointer dereferenceZack Rusin2009-07-062-0/+4
| | | | | | | | | | | | reported by clang static analyzer
* | | cso: possible null pointer dereferenceZack Rusin2009-07-061-0/+4
| | | | | | | | | | | | reported by clang static analyzer
* | | util: fix possible null pointer usageZack Rusin2009-07-064-11/+46
| | | | | | | | | | | | found by the clang static analyzer
* | | exa: some infrastucture work for accelerating compositeZack Rusin2009-07-065-49/+130
| | |
* | | radeon: ensure cmdbuf space for state + AOS is availableDave Airlie2009-07-061-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The problem is if we find out later we don't have any cmdbuf space but we've already written the arrays to the DMA buffer object, we end up emitting the current cmdbuf which has references to the current DMA object we then send that to the hw and we can't reference the arrays we just emitted to the old DMA buffer. things go bad, crash boom. This can probably be tuned further + swtcl probably needs some fixes
* | | r200: fix makefileDave Airlie2009-07-061-1/+1
| | |
* | | radeon: fixup FBO depth 24 allocations to avoid assertDave Airlie2009-07-061-3/+3
| | |
* | | radeon/r200/r300: port to new space checking code in libdrmDave Airlie2009-07-0616-223/+417
| | | | | | | | | | | | | | | This moves a big chunk of the space checking code into libdrm so it can be shared by the DDX.
* | | radeon-gallium: Compile warning fix.Corbin Simpson2009-07-051-1/+1
| | | | | | | | | | | | Fixes flush during validation, in case a buffer is double-validated.
* | | radeon-gallium: Use FLINK to do proper global buffers.Corbin Simpson2009-07-053-2/+26
| | |
* | | radeon-gallium: Wait for BOs before mapping them.Corbin Simpson2009-07-051-0/+2
| | |
* | | r300: fix vertex limitsMaciej Cencora2009-07-052-22/+7
| | | | | | | | | | | | | | | | | | | | | - don't limit vertex count if we are using indices - max indices count is 65535 not 65536 - remove some comments that don't apply anymore - remove unreachable code
* | | Merge branch 'mesa_7_5_branch'Jakob Bornecrantz2009-07-0346-347/+6040
|\ \ \ | | |/ | |/| | | | | | | | | | 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.
| * | progs: revert damage to progs/SConscript from recent compressed texture commitKeith Whitwell2009-07-031-0/+9
| | |
| * | mesa/shaders: fix gl_NormalMatrix state parametersKeith Whitwell2009-07-031-1/+1
| | | | | | | | | | | | | | | | | | gl_NormalMatrix is the inverse transpose of the modelview matrix, but as every matrix here needs to be transposed, we end up with {MODELVIEW_MATRIX, INVERSE}.
| * | st/wgl: don't advertise WGL_EXT_swap_interval stringKeith Whitwell2009-07-031-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is a tweak to a previous fix -- it's not necessary to actually advertise this extension to prevent these games from crashing -- they ignore the extension string anyway. It's sufficient to just have GetProcAddress return some dummy function addresses for SwapInterval. Given we don't really implement this funcitonality, this is a better fix.
| * | wgl: Lookup framebuffers by HWND whenever possible.José Fonseca2009-07-031-0/+10
| | | | | | | | | | | | | | | Some applications create several HDCs for the same window, so spite the WGL API is geared towards HDCs it is not reliable searching by HDC.
| * | mesa: Assume depth textures have a single level unless told otherwise.José Fonseca2009-07-021-1/+3
| | |
| * | mesa: s/TRUE/GL_TRUEKeith Whitwell2009-07-021-1/+1
| | | | | | | | | | | | Fix compile breakage on Linux.
| * | glapi: ensure _mesa_lookup_prim_by_nr() is not clobbered on regenerationKeith Whitwell2009-07-021-0/+23
| | | | | | | | | | | | Propogate changes to enums.c back up to the python source.
| * | Merge commit 'origin/dlist-statechange-shortcircuit' into mesa_7_5_branchKeith Whitwell2009-07-0214-37/+1011
| |\ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Conflicts: progs/trivial/Makefile Pull in a minimal version of statechange shortcircuiting in display list compilation. This affects only glMaterial and glShadeModel state, and includes quite a few tests to exercise various tricky cases. If this goes well, will consider extending to all state in the future.
| | * | mesa/vbo: fix compile and replay of nodes ending in a FALLBACKKeith Whitwell2009-06-303-13/+187
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Where vbo save nodes are terminated with a call to DO_FALLBACK(), as in the case of a recursive CallList which is itself within a Begin/End pair, there two problems: 1) The display list node's primitive information was incorrect, stating the cut-off prim had zero vertices 2) On replay, we would get confused by a primitive that started in a node, but was terminated by individual opcodes. This change fixes the first problem by correctly terminating the last primitive on fallback, and the second by forcing the display list to use the Loopback path, converting all nodes into immediate-mode rendering. The loopback fix is a performance hit, but avoiding this would require a fairly large rework of this code.
| | * | mesa/dlist: fixes and improvements for material cachingKeith Whitwell2009-06-301-8/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Only short-circuit material call if *all* statechanges from this call are cached. Some material calls (eg with FRONT_AND_BACK) change more than one piece of state -- need to check all of them before returning. Also, Material calls are legal inside begin/end pairs, so don't need to be as careful about begin/end state as with regular statechanges (like ShadeModel) when caching. Take advantage of this and do better caching.
| | * | progs/trivial: add dlist-mat-tri.cKeith Whitwell2009-06-302-0/+183
| | | |
| | * | progs/trivial: add test case for short-circuiting material changesKeith Whitwell2009-06-302-0/+175
| | | | | | | | | | | | | | | | | | | | Similar to dlist-tri-flat-tri, but using glMaterial calls, which have the extra property of being legal within Begin/End calls.
| | * | mesa/dlist: don't cache state which may not be replayed on CallListKeith Whitwell2009-06-301-1/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Statechanges which occur before the first End in a display list may not be replayed when the list is called, in particular if it is called from within a begin/end pair. Recognize vulnerable statechanges and do not use them to fill in the state cache.
| | * | progs/trivial: add dlist-flat-tri.cKeith Whitwell2009-06-302-0/+172
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | State-change functions which precede the first call to glEnd() in a compiled list are vulnerable to not being executed when that list is called. In particular this can happen if a list is invoked from within a begin/end pair, as in this example.
| | * | mesa/dlist: invalidate cached dlist compile state after CallListKeith Whitwell2009-06-301-16/+24
| | | | | | | | | | | | | | | | | | | | | | | | When compiling a display list containing a CallList, it is necessary to invalidate any assumption about the GL state after the recursive call completes.
| | * | progs/trivial: add dlist-recursive-callKeith Whitwell2009-06-302-0/+191
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When one display list calls another display list, it is possible that the calling display list makes state-changes or other actions which invalidate any attempt at caching or state-change elimination in the calling list. This test exercises one such case, where the called list consists of just a single glShadeModel() call.
| | * | dlist-tri-flat-tri: make tri render differently if flatshade not enabledKeith Whitwell2009-06-301-1/+3
| | | | | | | | | | | | | | | | | | | | When testing flat-shading, it helps to specify per-vertex colors so that you can distinguish between flat & smooth shading.
| | * | Merge branch 'mesa_7_5_branch' into dlist-statechange-shortcircuitKeith Whitwell2009-06-3015-272/+345
| | |\ \ | | | | | | | | | | | | | | | Need this to pick up fixes for per-vertex materials.
| | * | | progs/trivial: test case for dlist statechange eliminationKeith Whitwell2009-06-302-0/+170
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Creates a display list with redundant call to glShadeModel. View dlist contents with MESA_VERBOSE=list
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-17 14:53:59 +0000