search for: st_context

...07ffff0cf5bec in nvc0_shader_stage (pipe=<optimized out>) at ./nvc0/nvc0_context.h:204 nvc0_set_constant_buffer (pipe=0x631080, shader=<optimized out>, index=<optimized out>, cb=0x0) at nvc0/nvc0_state.c:771 0x00007ffff0a2cf63 in st_destroy_context (st=0x68a9f0) at state_tracker/st_context.c:382 ... Signed-off-by: Tobias Klausmann <tobias.johannes.klausmann at mni.thm.de> --- src/gallium/drivers/nouveau/nvc0/nvc0_context.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/gallium/drivers/nouveau/nvc0/nvc0_context.h b/src/gallium/drivers/nouveau/nvc0/...

--- src/gallium/drivers/nv40/nv40_fragprog.c | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git a/src/gallium/drivers/nv40/nv40_fragprog.c b/src/gallium/drivers/nv40/nv40_fragprog.c index 1237066..209d211 100644 --- a/src/gallium/drivers/nv40/nv40_fragprog.c +++ b/src/gallium/drivers/nv40/nv40_fragprog.c @@ -843,7 +843,8 @@ nv40_fragprog_translate(struct nv40_context *nv40,

...w one could do so_data (so, fui(-(nv50->viewport.translate[1] - nv50->framebuffer.height)); as well, which would make the viewport transformation correct, but the ST still outputs the wrong vertex coordinates for clear_with_quad. To fix both things, one could just let st_fb_orientation in st_context.h return Y_0_BOTTOM, but then glCopyTexSubImage2D (calling the appropriate function in st_cb_texture.c) flips the image and copies from the wrong offset, since offset 0 in memory is, well, top, as opposed to bottom like it seems to be for vertex coordinates that bypass the viewport ... Anyway, I...

...in pipe_resource_reference (ptr=0xfeeae8, tex=0x0) at ../../../../src/gallium/auxiliary/util/u_inlines.h:121 #3 0x00007f4a758b142b in nv50_set_constant_buffer (pipe=0xfee5d0, shader=3, index=0, cb=0x0) at nv50_state.c:761 #4 0x00007f4a75a97846 in st_destroy_context (st=0x1081550) at state_tracker/st_context.c:291 #5 0x00007f4a75960add in st_context_destroy (stctxi=0x1081550) at state_tracker/st_manager.c:596 #6 0x00007f4a75868a74 in dri_destroy_context (cPriv=0xfee590) at dri_context.c:174 #7 0x00007f4a75861b4b in driDestroyContext (pcp=0xfee590) at ../../../../src/mesa/drivers/dri/common/dri_util....

...ions(-) diff --git a/src/mesa/state_tracker/st_atom_framebuffer.c b/src/mesa/state_tracker/st_atom_framebuffer.c index ea41d9d..3ee4ea5 100644 --- a/src/mesa/state_tracker/st_atom_framebuffer.c +++ b/src/mesa/state_tracker/st_atom_framebuffer.c @@ -177,8 +177,10 @@ update_framebuffer_state( struct st_context *st ) /* rendering to a GL texture, may have to update surface */ st_update_renderbuffer_surface(st, strb); } - pipe_surface_reference(&framebuffer->zsbuf, strb->surface); - update_framebuffer_size(framebuffer, strb->surface); + if (strb->sur...

This CAP will determine whether ARB_framebuffer_object can be enabled. The nv30 driver does not allow mixing swizzled and linear zsbuf/cbuf textures. Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- src/gallium/docs/source/screen.rst | 3 +++ src/gallium/drivers/freedreno/freedreno_screen.c | 1 + src/gallium/drivers/i915/i915_screen.c | 1 +

..., num_src ); + src, num_src, 0); break; } } diff --git a/src/mesa/state_tracker/st_pbo.c b/src/mesa/state_tracker/st_pbo.c index 303c8535b2..3dff1609e8 100644 --- a/src/mesa/state_tracker/st_pbo.c +++ b/src/mesa/state_tracker/st_pbo.c @@ -528,7 +528,7 @@ create_fs(struct st_context *st, bool download, enum pipe_texture_target target, op[0] = ureg_src(temp0); op[1] = ureg_src(temp1); ureg_memory_insn(ureg, TGSI_OPCODE_STORE, &out, 1, op, 2, 0, - TGSI_TEXTURE_BUFFER, PIPE_FORMAT_NONE); + TGSI_TEXTU...

http://bugs.freedesktop.org/show_bug.cgi?id=23505 Summary: KDE's Kubrick has problems with xf86-video-nouveau driver Product: Mesa Version: git Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau AssignedTo: nouveau at

Running Tomb Raider on Nouveau I found some flicker caused by ignoring precise modifiers on variables inside Nouveau. This series add precise/invariant handling to TGSI, which can be then used by drivers to disable certain unsafe optimisations which may otherwise alter calculations, which depend on having the same result across shaders. This series fixes this bug in Tomb Raider and one CTS test

This patch series adds the needed support for this extension to the various parts of mesa to finally enable it for nvc0. Dave Airlie (1): glsl: lower cull_distance into cull_distance_mesa Tobias Klausmann (10): glapi: add GL_ARB_cull_distance mesa/main: add support for GL_ARB_cull_distance mesa/prog: Add varyings for arb_cull_distance mesa/st: add support for GL_ARB_cull_distance