search for: vertex_data

Mesa sometimes hands us large user buffers where only a few vertices are read from in the drawing calls before they change again. In such cases, allocating a new buffer from the kernel and copying all the data takes much too long, so this patch uses NV50TCL_VERTEX_DATA to push vertices on the FIFO, which speeds up e.g. nexuiz quite a lot. Additionally it gets rid of the issue that the card uses garbage as vertex data, which is probably an issue we should still investigate further. Maybe using memcpy to upload data doesn't invalidate caches on the GPU sid...

Signed-off-by: Maarten Maathuis <madman2003 at gmail.com> --- src/gallium/drivers/nouveau/nouveau_stateobj.h | 9 +++++++++ 1 files changed, 9 insertions(+), 0 deletions(-) diff --git a/src/gallium/drivers/nouveau/nouveau_stateobj.h b/src/gallium/drivers/nouveau/nouveau_stateobj.h index 9aee9e4..6c40f64 100644 --- a/src/gallium/drivers/nouveau/nouveau_stateobj.h +++

--- rnndb/nv50_pgraph.xml | 3 +++ 1 files changed, 3 insertions(+), 0 deletions(-) diff --git a/rnndb/nv50_pgraph.xml b/rnndb/nv50_pgraph.xml index 92d69ea..6499631 100644 --- a/rnndb/nv50_pgraph.xml +++ b/rnndb/nv50_pgraph.xml @@ -93,6 +93,9 @@ <value value="0x23" name="XY_OUT_OF_BOUNDS"> <!-- m2mf at least. 2d too? --> <brief>Your x/y coords

...o why this case works under nvc0+ hardware and does not under nv50. Here are some of the things I've noticed: * nvc0 uses immediate(s) for VERTEX_BEGIN_GL/VERTEX_END_GL * nvc0 is more consistent for doing pushbuffer space checks * nvc0 uses dirty tracking in set_index_buffer() * nvc0 uses "VERTEX_DATA push mode" over the FIFO for nv50 AFAICS the second and third one have no effect when ported to nv50. I'm highly suspecting that "push mode" or actually the type of buffers used will be the solution to this problem. Would you have any input/ideas? It would be nice to have this...

This patchset applies some minor fixes to renouveau.xml and then unifies the nv30 and nv40 register definitions. nv30 and nv40 are very similar and have the same offsets for the registers they share. The major differences are: 1. Texture setup is different due to full NPOT support on nv40 2. More advanced blending/render targets on nv40 3. NV30 has fixed function registers, which NV40 lacks The