fdo-mirrors/mesa
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/mesa/mesa.git synced 2026-01-19 04:30:25 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

r300: Always emit LOAD_VBPNTR immediately before index-based rendering

Browse source 
This fixes one type of lockup I've been seeing on my test system.
This commit is contained in:
Nicolai Haehnle 2008-07-26 16:15:33 +02:00
parent 9bc9e0ecb0
commit 477fa8fe12
1 changed files with 12 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
src/mesa/drivers/dri/r300/r300_render.c
View file

@ -269,13 +269,24 @@ static void r300RunRenderPrimitive(r300ContextPtr rmesa, GLcontext * ctx,
return;
if (vb->Elts) {
r300EmitAOS(rmesa, rmesa->state.aos_count, start);
if (num_verts > 65535) {
/* not implemented yet */
WARN_ONCE("Too many elts\n");
return;
}
/* Note: The following is incorrect, but it's the best I can do
* without a major refactoring of how DMA memory is handled.
* The problem: Ensuring that both vertex arrays *and* index
* arrays are at the right position, and then ensuring that
* the LOAD_VBPNTR, DRAW_INDX and INDX_BUFFER packets are emitted
* at once.
*
* So why is the following incorrect? Well, it seems like
* allocating the index array might actually evict the vertex
* arrays. *sigh*
*/
r300EmitElts(ctx, vb->Elts, num_verts);
r300EmitAOS(rmesa, rmesa->state.aos_count, start);
r300FireEB(rmesa, rmesa->state.elt_dma.aos_offset, num_verts, type);
} else {
r300EmitAOS(rmesa, rmesa->state.aos_count, start);