search for: nv30_miptree

Fixes FDO#55294. --- src/gallium/drivers/nv30/nv30_miptree.c | 3 +-- src/gallium/drivers/nv50/nv50_miptree.c | 3 +-- 2 files changed, 2 insertions(+), 4 deletions(-) diff --git a/src/gallium/drivers/nv30/nv30_miptree.c b/src/gallium/drivers/nv30/nv30_miptree.c index 5a9a63b..9700fa8 100644 --- a/src/gallium/drivers/nv30/nv30_miptree.c +++ b/src/gallium/...

...gt; This commit divides the sources and dest surfaces in to tiles which > match the constraints of the sifm object, so that color resolving > will work properly on nv3x cards. > > Signed-off-by: Hans de Goede <hdegoede at redhat.com> > --- > src/gallium/drivers/nouveau/nv30/nv30_miptree.c | 55 ++++++++++++++++++++++++- > 1 file changed, 54 insertions(+), 1 deletion(-) > > diff --git a/src/gallium/drivers/nouveau/nv30/nv30_miptree.c b/src/gallium/drivers/nouveau/nv30/nv30_miptree.c > index 76bb8b8..c240030 100644 > --- a/src/gallium/drivers/nouveau/nv30/nv30_miptree...

...nstraints of the sifm object, so that color resolving will work properly on nv3x cards. Signed-off-by: Hans de Goede <hdegoede at redhat.com> --- Changes in v2: -Use 1024x1024 blocks -Use the sifm on both nv3x and nv4x cards instead of only on nv3x cards --- src/gallium/drivers/nouveau/nv30/nv30_miptree.c | 38 ++++++++++++++++++++++++- 1 file changed, 37 insertions(+), 1 deletion(-) diff --git a/src/gallium/drivers/nouveau/nv30/nv30_miptree.c b/src/gallium/drivers/nouveau/nv30/nv30_miptree.c index 76bb8b8..735c718 100644 --- a/src/gallium/drivers/nouveau/nv30/nv30_miptree.c +++ b/src/gallium/dri...

Hi All, Here is a bunch of fixes for nv30 cards, the first patch is a resend of a patch I send a while back. AFAICT that one is ready for merging, but it is not entirely clear to me what the process is for getting (nouveau) mesa patches merged. Should I request commit rights, and push my own patches once they have been reviewed ? Regards, Hans

On Thu, Sep 3, 2015 at 7:25 AM, Hans de Goede <hdegoede at redhat.com> wrote: > On nv3x we will likely end up using the cpu to do color resolving for msaa > blits. Disable msaa on these cards so that we do not end up using the cpu. Actually the CPU fallback won't do scaled, so it's stuck with SIFM or assert(false). Which isn't great, but... it's what the HW does. I

The sifm object has a limit of 1024x1024 for its input size and 2048x2048 for its output. The code checking this was trying to be clever resulting in it seeing a surface of e.g 1024x256 being outside of the input size limit. This commit fixes this. Signed-off-by: Hans de Goede <hdegoede at redhat.com> --- src/gallium/drivers/nouveau/nv30/nv30_transfer.c | 4 ++-- 1 file changed, 2

...ce and caches the result in a static variable. --- src/gallium/drivers/nv04/nv04_transfer.c | 6 ++++-- src/gallium/drivers/nv10/nv10_transfer.c | 6 ++++-- src/gallium/drivers/nv20/nv20_miptree.c | 5 ++++- src/gallium/drivers/nv20/nv20_transfer.c | 6 ++++-- src/gallium/drivers/nv30/nv30_miptree.c | 5 ++++- src/gallium/drivers/nv30/nv30_transfer.c | 6 ++++-- src/gallium/drivers/nv40/nv40_miptree.c | 5 ++++- src/gallium/drivers/nv40/nv40_transfer.c | 6 ++++-- 8 files changed, 32 insertions(+), 13 deletions(-) diff --git a/src/gallium/drivers/nv04/nv04_transfer.c b/src/gal...

...>>>> >>>> I discussed this with Ben this morning and he suggested that this >>>> is likely a Mesa issue since with DRI3 mesa rather then the ddx >>>> allocs the surfaces. I've tried disabling swizzling in the >>>> mesa code by forcing nv30_miptree_create() to always take >>>> the code path for linear textures, but that leads to the exact >>>> same result as before that change. >>> >>> >>> Ah yes. Very different problem indeed. I actually suspect it has to do >>> with swizzling. Look...

Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- src/gallium/drivers/nouveau/nv30/nv30_screen.c | 33 +++++++++++++------------- 1 file changed, 17 insertions(+), 16 deletions(-) diff --git a/src/gallium/drivers/nouveau/nv30/nv30_screen.c b/src/gallium/drivers/nouveau/nv30/nv30_screen.c index 4baabaf..5c3d783 100644 --- a/src/gallium/drivers/nouveau/nv30/nv30_screen.c +++

...rivers/nv20/nv20_state.h | 13 -- src/gallium/drivers/nv20/nv20_state_emit.c | 12 +- src/gallium/drivers/nv20/nv20_transfer.c | 178 --------------------- src/gallium/drivers/nv30/Makefile | 2 - src/gallium/drivers/nv30/nv30_fragtex.c | 8 +- src/gallium/drivers/nv30/nv30_miptree.c | 239 ---------------------------- src/gallium/drivers/nv30/nv30_screen.c | 13 +-- src/gallium/drivers/nv30/nv30_state.h | 13 -- src/gallium/drivers/nv30/nv30_state_fb.c | 20 ++-- src/gallium/drivers/nv30/nv30_transfer.c | 178 --------------------- src/gallium/drivers...

...rivers/nv20/nv20_state_emit.c | 14 +- src/gallium/drivers/nv20/nv20_transfer.c | 178 --------------------- src/gallium/drivers/nv30/Makefile | 2 - src/gallium/drivers/nv30/nv30_context.h | 2 +- src/gallium/drivers/nv30/nv30_fragtex.c | 8 +- src/gallium/drivers/nv30/nv30_miptree.c | 239 ---------------------------- src/gallium/drivers/nv30/nv30_screen.c | 13 +-- src/gallium/drivers/nv30/nv30_state.h | 13 -- src/gallium/drivers/nv30/nv30_state_fb.c | 20 ++-- src/gallium/drivers/nv30/nv30_transfer.c | 178 --------------------- src/gallium/drivers...

...leading to >> software rendering. >> >> I discussed this with Ben this morning and he suggested that this >> is likely a Mesa issue since with DRI3 mesa rather then the ddx >> allocs the surfaces. I've tried disabling swizzling in the >> mesa code by forcing nv30_miptree_create() to always take >> the code path for linear textures, but that leads to the exact >> same result as before that change. > > Ah yes. Very different problem indeed. I actually suspect it has to do > with swizzling. Look at the white pattern of the moon -- it's all in...

...---- src/gallium/drivers/nv20/nv20_surface.c | 63 -- src/gallium/drivers/nv20/nv20_transfer.c | 178 ----- src/gallium/drivers/nv20/nv20_vbo.c | 79 -- src/gallium/drivers/nv20/nv20_vertprog.c | 841 -------------------- src/gallium/drivers/nv30/nv30_miptree.c | 2 +- src/gallium/drivers/nv30/nv30_screen.h | 2 +- src/gallium/drivers/nv40/nv40_miptree.c | 2 +- src/gallium/drivers/nv40/nv40_screen.h | 2 +- src/gallium/winsys/drm/nouveau/dri/Makefile | 3 - .../winsys/drm/nouveau/drm/n...