search for: nv30_screen

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

...great, but... it's what the HW does. I don't see a reason to shut that off. I'd rather disallow allocating MS surfaces that SIFM won't later be able to resolve on nv3x. > Signed-off-by: Hans de Goede <hdegoede at redhat.com> > --- > src/gallium/drivers/nouveau/nv30/nv30_screen.c | 12 ++++++++++-- > 1 file changed, 10 insertions(+), 2 deletions(-) > > diff --git a/src/gallium/drivers/nouveau/nv30/nv30_screen.c b/src/gallium/drivers/nouveau/nv30/nv30_screen.c > index 7aad26b..69acc38 100644 > --- a/src/gallium/drivers/nouveau/nv30/nv30_screen.c > +++ b/s...

...putting queries in a linked list and waiting on the oldest one if allocation fails. nVidia seems to use a similar strategy, but with 1024 instead of 32 fences. The next patch will improve this. --- src/gallium/drivers/nv30/nv30_query.c | 26 ++++++++++++++++++-------- src/gallium/drivers/nv30/nv30_screen.c | 2 ++ src/gallium/drivers/nv30/nv30_screen.h | 1 + src/gallium/drivers/nv40/nv40_query.c | 26 ++++++++++++++++++-------- src/gallium/drivers/nv40/nv40_screen.c | 2 ++ src/gallium/drivers/nv40/nv40_screen.h | 1 + 6 files changed, 42 insertions(+), 16 deletions(-) diff --git a...

Add missing PIPE_SHADER_CAP_INTEGERS for frag shaders to nv30_screen_get_shader_param(). Signed-off-by: Hans de Goede <hdegoede at redhat.com> --- src/gallium/drivers/nouveau/nv30/nv30_screen.c | 1 + 1 file changed, 1 insertion(+) diff --git a/src/gallium/drivers/nouveau/nv30/nv30_screen.c b/src/gallium/drivers/nouveau/nv30/nv30_screen.c index db7c2d1..ece...

It should be possible to make this be 16 on nvc0. Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- Not touching nv50 since I have a patch that actually impelents support for multiple viewports there. src/gallium/drivers/nouveau/nv30/nv30_screen.c | 2 ++ src/gallium/drivers/nouveau/nvc0/nvc0_screen.c | 2 ++ 2 files changed, 4 insertions(+) diff --git a/src/gallium/drivers/nouveau/nv30/nv30_screen.c b/src/gallium/drivers/nouveau/nv30/nv30_screen.c index 8eee06b..c027a5f 100644 --- a/src/gallium/drivers/nouveau/nv30/nv30_screen.c +++ b/sr...

...m by allowing the winsys to detect whether > the pipe driver's destroy function needs to be called or not. > > Signed-off-by: Ben Skeggs <bskeggs at redhat.com> > --- > src/gallium/drivers/nouveau/nouveau_screen.c | 8 ++++++-- > src/gallium/drivers/nouveau/nv30/nv30_screen.c | 19 ++++++++++--------- > src/gallium/drivers/nouveau/nv50/nv50_screen.c | 6 +++--- > src/gallium/drivers/nouveau/nvc0/nvc0_screen.c | 9 ++++----- > src/gallium/winsys/nouveau/drm/nouveau_drm_winsys.c | 16 ++++++++++------ > 5 files changed, 33 insertions(+), 25...

...oldest one if allocation fails. nVidia seems to use a similar strategy, but with 1024 instead of 32 fences. The next patch will improve this. Fixed indentation and added header for query_list. --- src/gallium/drivers/nv30/nv30_query.c | 26 ++++++++++++++++++-------- src/gallium/drivers/nv30/nv30_screen.c | 2 ++ src/gallium/drivers/nv30/nv30_screen.h | 2 ++ src/gallium/drivers/nv40/nv40_query.c | 26 ++++++++++++++++++-------- src/gallium/drivers/nv40/nv40_screen.c | 2 ++ src/gallium/drivers/nv40/nv40_screen.h | 2 ++ 6 files changed, 44 insertions(+), 16 deletions(-) diff --git...

...gt;> the pipe driver's destroy function needs to be called or not. >>> >>> Signed-off-by: Ben Skeggs <bskeggs at redhat.com> >>> --- >>> src/gallium/drivers/nouveau/nouveau_screen.c | 8 ++++++-- >>> src/gallium/drivers/nouveau/nv30/nv30_screen.c | 19 ++++++++++--------- >>> src/gallium/drivers/nouveau/nv50/nv50_screen.c | 6 +++--- >>> src/gallium/drivers/nouveau/nvc0/nvc0_screen.c | 9 ++++----- >>> src/gallium/winsys/nouveau/drm/nouveau_drm_winsys.c | 16 ++++++++++------ >>> 5 file...

...;t been emitted...). I figure it doesn't really matter enough to worry about that. The bigger reason to do it, I guess, is to make sure that all the fences on the list get processed. But perhaps it'd be OK to just nuke them without regard for such details? src/gallium/drivers/nouveau/nv30/nv30_screen.c | 14 ++++++++++---- src/gallium/drivers/nouveau/nv50/nv50_screen.c | 11 +++++++++-- src/gallium/drivers/nouveau/nvc0/nvc0_screen.c | 9 ++++++++- 3 files changed, 27 insertions(+), 7 deletions(-) diff --git a/src/gallium/drivers/nouveau/nv30/nv30_screen.c b/src/gallium/drivers/nouveau/nv30/nv...

...This commit fixes the problem by allowing the winsys to detect whether the pipe driver's destroy function needs to be called or not. Signed-off-by: Ben Skeggs <bskeggs at redhat.com> --- src/gallium/drivers/nouveau/nouveau_screen.c | 8 ++++++-- src/gallium/drivers/nouveau/nv30/nv30_screen.c | 19 ++++++++++--------- src/gallium/drivers/nouveau/nv50/nv50_screen.c | 6 +++--- src/gallium/drivers/nouveau/nvc0/nvc0_screen.c | 9 ++++----- src/gallium/winsys/nouveau/drm/nouveau_drm_winsys.c | 16 ++++++++++------ 5 files changed, 33 insertions(+), 25 deletions(-) diff -...

...{ struct nv40_context *nv40 = nv40_context(pipe); + unsigned i; + for (i = 0; i < NV40_STATE_MAX; i++) { + if (nv40->state.hw[i]) + so_ref(NULL, &nv40->state.hw[i]); + } + if (nv40->draw) draw_destroy(nv40->draw); FREE(nv40); Index: nv30/nv30_screen.c =================================================================== --- nv30/nv30_screen.c (wersja 32083) +++ nv30/nv30_screen.c (kopia robocza) @@ -153,7 +153,13 @@ nv30_screen_destroy(struct pipe_screen *pscreen) { struct nv30_screen *screen = nv30_screen(pscreen); + unsigned i; +...

...to detect whether >> the pipe driver's destroy function needs to be called or not. >> >> Signed-off-by: Ben Skeggs <bskeggs at redhat.com> >> --- >> src/gallium/drivers/nouveau/nouveau_screen.c | 8 ++++++-- >> src/gallium/drivers/nouveau/nv30/nv30_screen.c | 19 ++++++++++--------- >> src/gallium/drivers/nouveau/nv50/nv50_screen.c | 6 +++--- >> src/gallium/drivers/nouveau/nvc0/nvc0_screen.c | 9 ++++----- >> src/gallium/winsys/nouveau/drm/nouveau_drm_winsys.c | 16 ++++++++++------ >> 5 files changed, 33 in...

We do not have a generic blitter on nv3x cards, so we must use the sifm object for color resolving. 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> --- Changes in v2: -Use 1024x1024 blocks -Use the sifm on both nv3x

Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- Silences a warning about unrecognized param when in debug mode. src/gallium/drivers/nv30/nv30_screen.c | 1 + 1 file changed, 1 insertion(+) diff --git a/src/gallium/drivers/nv30/nv30_screen.c b/src/gallium/drivers/nv30/nv30_screen.c index 40e8b5f..39e64ce 100644 --- a/src/gallium/drivers/nv30/nv30_screen.c +++ b/src/gallium/drivers/nv30/nv30_screen.c @@ -113,6 +113,7 @@ nv30_screen_get_param(str...

...generic only allows for up to 10/8 texcoords for nv40/nv30. This fixes compilation of the varying-packing tests (although they still fail). Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> Cc: 9.1 9.2 10.0 <mesa-stable at lists.freedesktop.org> --- src/gallium/drivers/nouveau/nv30/nv30_screen.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/gallium/drivers/nouveau/nv30/nv30_screen.c b/src/gallium/drivers/nouveau/nv30/nv30_screen.c index 26ad33d..9ce10a4 100644 --- a/src/gallium/drivers/nouveau/nv30/nv30_screen.c +++ b/src/gallium/drivers/nouveau/nv30/nv30_screen...

Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> Cc: "10.2" <mesa-stable at lists.freedesktop.org> --- src/gallium/drivers/nouveau/nv30/nv30_screen.c | 6 ++++++ src/gallium/drivers/nouveau/nv30/nvfx_fragprog.c | 1 + 2 files changed, 7 insertions(+) diff --git a/src/gallium/drivers/nouveau/nv30/nv30_screen.c b/src/gallium/drivers/nouveau/nv30/nv30_screen.c index fb9378c..4baabaf 100644 --- a/src/gallium/drivers/nouveau/nv30/nv30_screen.c +...

From: Ben Skeggs <bskeggs at redhat.com> Signed-off-by: Ben Skeggs <bskeggs at redhat.com> --- configure.ac | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/configure.ac b/configure.ac index 4016871..c02ee61 100644 --- a/configure.ac +++ b/configure.ac @@ -73,7 +73,7 @@ LIBDRM_RADEON_REQUIRED=2.4.56 LIBDRM_AMDGPU_REQUIRED=2.4.63 LIBDRM_INTEL_REQUIRED=2.4.61

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 +++ b/src/gallium/dri...

...s/source/screen.rst | 3 +++ src/gallium/drivers/freedreno/freedreno_screen.c | 1 + src/gallium/drivers/i915/i915_screen.c | 1 + src/gallium/drivers/ilo/ilo_screen.c | 1 + src/gallium/drivers/llvmpipe/lp_screen.c | 1 + src/gallium/drivers/nouveau/nv30/nv30_screen.c | 1 + src/gallium/drivers/nouveau/nv50/nv50_screen.c | 1 + src/gallium/drivers/nouveau/nvc0/nvc0_screen.c | 1 + src/gallium/drivers/r300/r300_screen.c | 1 + src/gallium/drivers/r600/r600_pipe.c | 1 + src/gallium/drivers/radeonsi/radeonsi_pipe.c | 1 + src/gall...

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