Displaying 3 results from an estimated 3 matches for "vroute".
Did you mean:
route
2015 May 26
2
[PATCH 2/2] nv30/draw: switch varying hookup logic to know about texcoords
...[TGSI_SEMANTIC_PSIZE ] = { EMIT_1F_PSIZE, INTERP_POS , 6, 6, 0x00000020 },
> - [TGSI_SEMANTIC_GENERIC ] = { EMIT_4F, INTERP_PERSPECTIVE, 8, 7, 0x00004000 }
> + [TGSI_SEMANTIC_TEXCOORD] = { EMIT_4F, INTERP_PERSPECTIVE, 8, 7, 0x00004000 },
> };
>
> static boolean
> vroute_add(struct nv30_render *r, uint attrib, uint sem, uint *idx)
> {
> - struct pipe_screen *pscreen = &r->nv30->screen->base.base;
> + struct nv30_screen *screen = r->nv30->screen;
> struct nv30_fragprog *fp = r->nv30->fragprog.program;
> struct...
2015 May 26
2
[PATCH 2/2] nv30/draw: switch varying hookup logic to know about texcoords
...t; 0x00000020 },
>>> - [TGSI_SEMANTIC_GENERIC ] = { EMIT_4F, INTERP_PERSPECTIVE, 8, 7,
>>> 0x00004000 }
>>> + [TGSI_SEMANTIC_TEXCOORD] = { EMIT_4F, INTERP_PERSPECTIVE, 8, 7,
>>> 0x00004000 },
>>> };
>>> static boolean
>>> vroute_add(struct nv30_render *r, uint attrib, uint sem, uint *idx)
>>> {
>>> - struct pipe_screen *pscreen = &r->nv30->screen->base.base;
>>> + struct nv30_screen *screen = r->nv30->screen;
>>> struct nv30_fragprog *fp = r->nv30->f...
2015 May 25
3
[PATCH 1/2] nv30/draw: rework some of the output vertex buffer logic
This makes the vertex buffer go to GART, not VRAM, and redoes the
mapping to not use the UNSYNCHRONIZED access (which is meaningless on a
VRAM buffer anyways). While we're at it, add some flushes for VBO data.
Moving the vertex buffer from VRAM to GART makes glxgears work fully
with NV30_SWTNL=1. The other changes just seem like a good idea. I'm not
sure *why* moving the buffer from VRAM