search for: blit_3d

...ons(+), 2 deletions(-) diff --git a/src/gallium/drivers/nouveau/nv50/nv50_surface.c b/src/gallium/drivers/nouveau/nv50/nv50_surface.c index dc6d628..216e667 100644 --- a/src/gallium/drivers/nouveau/nv50/nv50_surface.c +++ b/src/gallium/drivers/nouveau/nv50/nv50_surface.c @@ -1069,7 +1069,7 @@ nv50_blit_3d(struct nv50_context *nv50, const struct pipe_blit_info *info) PUSH_DATAf(push, y0); PUSH_DATAf(push, z); BEGIN_NV04(push, NV50_3D(VTX_ATTR_2F_X(0)), 2); - PUSH_DATAf(push, 16384 << nv50_miptree(dst)->ms_x); + PUSH_DATAf(push, 16384/* << nv50_miptree(dst...

...tions(+), 8 deletions(-) diff --git a/src/gallium/drivers/nouveau/nv50/nv50_surface.c b/src/gallium/drivers/nouveau/nv50/nv50_surface.c index dc6d628..6073deb 100644 --- a/src/gallium/drivers/nouveau/nv50/nv50_surface.c +++ b/src/gallium/drivers/nouveau/nv50/nv50_surface.c @@ -977,6 +977,7 @@ nv50_blit_3d(struct nv50_context *nv50, const struct pipe_blit_info *info) float x0, x1, y0, y1, z; float dz; float x_range, y_range; + float x_output, y_output; blit->mode = nv50_blit_select_mode(info); blit->color_mask = nv50_blit_derive_color_mask(info); @@ -996,11 +997,14 @@ nv...

https://bugs.freedesktop.org/show_bug.cgi?id=78863 Priority: medium Bug ID: 78863 Assignee: nouveau at lists.freedesktop.org Summary: [nv50] errors when starts gnome-shell QA Contact: xorg-team at lists.x.org Severity: minor Classification: Unclassified OS: All Reporter: mattia.b89 at gmail.com

...nning a working version can cause a broken version to appear to work. Running max-texture-size clears it up nicely.) As you might expect, making format == GL_DEPTH_COMPONENT go to the fallback in st_TexSubImage at HEAD fixes it too, but I don't think that's desired. This ends up taking the blit_3d path in nv50_surface.c. Of note is that on nva0+, GL_DEPTH_COMPONENT16 seems to work fine, which is also where the Z16_MSX_LSR storage type appeared, so probably not a coincidence. But a bit surprising is that on nva0+ it does work for Z16, but still not for the other ones. Makes me think this is...

...ut exactly how to configure the HW for those situations, but I suspect that the fixes will be fairly small and self-contained. Note that there are also a bunch of EXT_framebuffer_multisample tests that are failing, but that has nothing to do with these changes. There's something wrong with the blit_3d function, at the very least to do with depth/stencil, but also some color tests fail as well. These patches are available at https://github.com/imirkin/mesa.git nv50-gs or https://github.com/imirkin/mesa/commits/nv50-gs for those who prefer a web ui. Bryan Cain (2): nv50/ir: delay calculation o...