Displaying 4 results from an estimated 4 matches for "shade_model".
2013 Jul 06
4
[Bug 66642] New: [nva5] Wrong provoking vertex is selected for flat attribute interpolation (clipping?)
https://bugs.freedesktop.org/show_bug.cgi?id=66642
Priority: medium
Bug ID: 66642
Assignee: nouveau at lists.freedesktop.org
Summary: [nva5] Wrong provoking vertex is selected for flat
attribute interpolation (clipping?)
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter:
2014 Feb 04
2
[PATCH 1/3] nv50: rework primid logic
Functionally identical but much simpler. Should also better integrate
with future layer/viewport changes/fixes.
Cc: 10.1 <mesa-stable at lists.freedesktop.org>
Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu>
---
Not *strictly* necessary in stable, but it will make backporting later fixes
easier. No regressions in piglit.
src/gallium/drivers/nouveau/nv50/nv50_program.c | 5
2009 Dec 30
4
[PATCH 1/3] nv50: remove vtxbuf stateobject after a referenced vtxbuf is mapped
- This avoids problematic "reloc'ed while mapped" messages and
some associated corruption as well.
Signed-off-by: Maarten Maathuis <madman2003 at gmail.com>
---
src/gallium/drivers/nouveau/nouveau_screen.c | 21 +++++++++++++++++++++
src/gallium/drivers/nouveau/nouveau_screen.h | 3 +++
src/gallium/drivers/nouveau/nouveau_stateobj.h | 13 +++++++++++++
2010 Feb 26
5
[PATCH 0/5] renouveau: nv30/nv40 unification
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