search for: nve4_screen_compute_setup

Displaying 16 results from an estimated 16 matches for "nve4_screen_compute_setup".

2015 Dec 02
3
NV50 compute support questions
...if (class_3d > NVE4_3D_CLASS) - return 0; break; default: return 0; @@ -574,11 +572,10 @@ nvc0_screen_init_compute(struct nvc0_screen *screen) case 0xd0: return nvc0_screen_compute_setup(screen, screen->base.pushbuf); case 0xe0: - return nve4_screen_compute_setup(screen, screen->base.pushbuf); case 0xf0: case 0x100: case 0x110: - return 0; + return nve4_screen_compute_setup(screen, screen->base.pushbuf); default: return -1; } Then as soon as I do startx (which starts gnome-shell) the machine freezes. This is...
2015 Dec 02
0
NV50 compute support questions
...return 0; > break; > default: > return 0; > @@ -574,11 +572,10 @@ nvc0_screen_init_compute(struct nvc0_screen *screen) > case 0xd0: > return nvc0_screen_compute_setup(screen, screen->base.pushbuf); > case 0xe0: > - return nve4_screen_compute_setup(screen, screen->base.pushbuf); > case 0xf0: > case 0x100: > case 0x110: > - return 0; > + return nve4_screen_compute_setup(screen, screen->base.pushbuf); > default: > return -1; > } > > Then as soon as I do startx (which...
2015 Dec 04
0
NV50 compute support questions
...gt;> return 0; >>> @@ -574,11 +572,10 @@ nvc0_screen_init_compute(struct nvc0_screen >>> *screen) >>> case 0xd0: >>> return nvc0_screen_compute_setup(screen, screen->base.pushbuf); >>> case 0xe0: >>> - return nve4_screen_compute_setup(screen, screen->base.pushbuf); >>> case 0xf0: >>> case 0x100: >>> case 0x110: >>> - return 0; >>> + return nve4_screen_compute_setup(screen, screen->base.pushbuf); >>> default: >>> return -1;...
2015 Dec 04
4
NV50 compute support questions
...break; >> default: >> return 0; >> @@ -574,11 +572,10 @@ nvc0_screen_init_compute(struct nvc0_screen *screen) >> case 0xd0: >> return nvc0_screen_compute_setup(screen, screen->base.pushbuf); >> case 0xe0: >> - return nve4_screen_compute_setup(screen, screen->base.pushbuf); >> case 0xf0: >> case 0x100: >> case 0x110: >> - return 0; >> + return nve4_screen_compute_setup(screen, screen->base.pushbuf); >> default: >> return -1; >> } >> &gt...
2015 Nov 20
2
NV50 compute support questions
Hi, On 20-11-15 17:07, Samuel Pitoiset wrote: > > > On 11/20/2015 11:36 AM, Hans de Goede wrote: >> Hi Samual, et al, > > Hi Hans, > >> >> In >> http://cgit.freedesktop.org/mesa/mesa/commit/src/gallium/drivers/nouveau?id=ff72440b40211326eda118232fabd53965410afd >> >> you write: "This compute support has been tested by >> Pierre
2014 Jun 06
3
[PATCH 1/3] gk110/ir: emit texbar the same way that the blob does
Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> Cc: "10.2" <mesa-stable at lists.freedestkop.org> --- src/gallium/drivers/nouveau/codegen/nv50_ir_emit_gk110.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/gallium/drivers/nouveau/codegen/nv50_ir_emit_gk110.cpp b/src/gallium/drivers/nouveau/codegen/nv50_ir_emit_gk110.cpp index b8d0d3e..d566c99
2014 Jun 17
0
[PATCH try 2 2/2] gallium/nouveau: move pushbuf and fences to context
...te this further before enabling it by default. */ if (debug_get_bool_option("NVC0_COMPUTE", FALSE)) - return nvc0_screen_compute_setup(screen, screen->base.pushbuf); + return nvc0_screen_compute_setup(screen); return 0; case 0xe0: - return nve4_screen_compute_setup(screen, screen->base.pushbuf); + return nve4_screen_compute_setup(screen); case 0xf0: case 0x100: case 0x110: @@ -586,11 +545,9 @@ nvc0_screen_create(struct nouveau_device *dev) struct nvc0_screen *screen; struct pipe_screen *pscreen; struct nouveau_object *chan; -...
2014 Jun 17
2
[PATCH try 2 1/2] gallium/nouveau: decouple nouveau_fence implementation from screen
Signed-off-by: Maarten Lankhorst <maarten.lankhorst at canonical.com> --- src/gallium/drivers/nouveau/nouveau_fence.c | 76 ++++++++++++------------- src/gallium/drivers/nouveau/nouveau_fence.h | 22 +++++-- src/gallium/drivers/nouveau/nouveau_screen.c | 9 +++ src/gallium/drivers/nouveau/nouveau_screen.h | 14 ++--- src/gallium/drivers/nouveau/nv30/nv30_context.c | 4 +-
2014 Jun 21
3
[Mesa-dev] [PATCH try 2 2/2] gallium/nouveau: move pushbuf and fences to context
...by default. > */ > if (debug_get_bool_option("NVC0_COMPUTE", FALSE)) > - return nvc0_screen_compute_setup(screen, screen->base.pushbuf); > + return nvc0_screen_compute_setup(screen); > return 0; > case 0xe0: > - return nve4_screen_compute_setup(screen, screen->base.pushbuf); > + return nve4_screen_compute_setup(screen); > case 0xf0: > case 0x100: > case 0x110: > @@ -586,11 +545,9 @@ nvc0_screen_create(struct nouveau_device *dev) > struct nvc0_screen *screen; > struct pipe_screen *pscreen; &...
2014 Jun 16
2
[PATCH 1/2] gallium/nouveau: decouple nouveau_fence implementation from screen
Signed-off-by: Maarten Lankhorst <maarten.lankhorst at canonical.com> --- src/gallium/drivers/nouveau/nouveau_fence.c | 76 ++++++++++++------------- src/gallium/drivers/nouveau/nouveau_fence.h | 22 +++++-- src/gallium/drivers/nouveau/nouveau_screen.c | 9 +++ src/gallium/drivers/nouveau/nouveau_screen.h | 14 ++--- src/gallium/drivers/nouveau/nv30/nv30_context.c | 4
2014 Nov 19
5
[PATCH v2 0/3] nouveau: support for custom VRAM domains
This series is to allow NVIDIA chips with shared memory to operate more efficiently (and to operate at all once we disable VRAM from the kernel driver) by allowing nouveau_screen to specify a domain to use for objects originally allocated into VRAM. If the domain is not overridden, the default NOUVEAU_BO_VRAM is used. A NV_VRAM_DOMAIN() macro is then introduced to be used in place of
2014 Nov 19
0
[PATCH v2 2/3] nvc0: use NV_VRAM_DOMAIN() macro
...flush = TRUE; } diff --git a/src/gallium/drivers/nouveau/nvc0/nve4_compute.c b/src/gallium/drivers/nouveau/nvc0/nve4_compute.c index f243316b899c..fce02a7cc576 100644 --- a/src/gallium/drivers/nouveau/nvc0/nve4_compute.c +++ b/src/gallium/drivers/nouveau/nvc0/nve4_compute.c @@ -63,7 +63,7 @@ nve4_screen_compute_setup(struct nvc0_screen *screen, return ret; } - ret = nouveau_bo_new(dev, NOUVEAU_BO_VRAM, 0, NVE4_CP_PARAM_SIZE, NULL, + ret = nouveau_bo_new(dev, NV_VRAM_DOMAIN(&screen->base), 0, NVE4_CP_PARAM_SIZE, NULL, &screen->parm); if (ret) ret...
2014 Nov 19
1
[PATCH v2 2/3] nvc0: use NV_VRAM_DOMAIN() macro
...t; diff --git a/src/gallium/drivers/nouveau/nvc0/nve4_compute.c b/src/gallium/drivers/nouveau/nvc0/nve4_compute.c > index f243316b899c..fce02a7cc576 100644 > --- a/src/gallium/drivers/nouveau/nvc0/nve4_compute.c > +++ b/src/gallium/drivers/nouveau/nvc0/nve4_compute.c > @@ -63,7 +63,7 @@ nve4_screen_compute_setup(struct nvc0_screen *screen, > return ret; > } > > - ret = nouveau_bo_new(dev, NOUVEAU_BO_VRAM, 0, NVE4_CP_PARAM_SIZE, NULL, > + ret = nouveau_bo_new(dev, NV_VRAM_DOMAIN(&screen->base), 0, NVE4_CP_PARAM_SIZE, NULL, > &screen-...
2014 Nov 19
1
[PATCH v2 2/3] nvc0: use NV_VRAM_DOMAIN() macro
...t; diff --git a/src/gallium/drivers/nouveau/nvc0/nve4_compute.c b/src/gallium/drivers/nouveau/nvc0/nve4_compute.c > index f243316b899c..fce02a7cc576 100644 > --- a/src/gallium/drivers/nouveau/nvc0/nve4_compute.c > +++ b/src/gallium/drivers/nouveau/nvc0/nve4_compute.c > @@ -63,7 +63,7 @@ nve4_screen_compute_setup(struct nvc0_screen *screen, > return ret; > } > > - ret = nouveau_bo_new(dev, NOUVEAU_BO_VRAM, 0, NVE4_CP_PARAM_SIZE, NULL, > + ret = nouveau_bo_new(dev, NV_VRAM_DOMAIN(&screen->base), 0, NVE4_CP_PARAM_SIZE, NULL, > &screen->pa...
2014 Oct 27
4
[PATCH 0/3] nouveau: support for custom VRAM domains
This series is to allow NVIDIA chips with shared memory to operate more efficiently (and to operate at all once we disable VRAM from the kernel driver) by allowing nouveau_screen to specify a domain to use for objects originally allocated into VRAM. If the domain is not overridden, the default NOUVEAU_BO_VRAM is used. A NV_VRAM_DOMAIN() macro is then introduced to be used in place of
2015 Jun 19
5
[PATCH v3 0/2] nouveau: support for custom VRAM domains
New revision of this patchset that prevents VRAM objects from being allocated on VRAM-less systems like Tegra. This is required for Mesa to work on such systems. Changes since v2: - Use vram_size to detect systems without VRAM and set the correct domain instead of expecting each chip to set its domain explicitly. Alexandre Courbot (2): nouveau: support for custom VRAM domains nvc0: use