search for: nv30_swtnl

Displaying 10 results from an estimated 10 matches for "nv30_swtnl".

2015 Sep 12
9
[Bug 91986] New: Artifacts in models rendering with GeForce 6150 (NV4x chipsets)
https://bugs.freedesktop.org/show_bug.cgi?id=91986 Bug ID: 91986 Summary: Artifacts in models rendering with GeForce 6150 (NV4x chipsets) Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component:
2016 Apr 23
9
[Bug 95095] New: NV46 (G72) Full screen artifacts in Freespace 2 SW OT mod
https://bugs.freedesktop.org/show_bug.cgi?id=95095 Bug ID: 95095 Summary: NV46 (G72) Full screen artifacts in Freespace 2 SW OT mod Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau
2017 Jan 13
32
[Bug 99400] New: garbled rending with glamor on G71
https://bugs.freedesktop.org/show_bug.cgi?id=99400 Bug ID: 99400 Summary: [nouveau] garbled rending with glamor on G71 Product: Mesa Version: unspecified Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau Assignee: nouveau at
2015 May 25
3
[PATCH 1/2] nv30/draw: rework some of the output vertex buffer logic
This makes the vertex buffer go to GART, not VRAM, and redoes the mapping to not use the UNSYNCHRONIZED access (which is meaningless on a VRAM buffer anyways). While we're at it, add some flushes for VBO data. Moving the vertex buffer from VRAM to GART makes glxgears work fully with NV30_SWTNL=1. The other changes just seem like a good idea. I'm not sure *why* moving the buffer from VRAM makes it work... perhaps something doesn't get flushed in time? However this is a single use by the GPU buffer, so STREAM seems like the correct usage semantic for it. Signed-off-by: Ilia Mirkin...
2012 Oct 28
4
[Bug 56474] New: 3D app segfaults on NV46
https://bugs.freedesktop.org/show_bug.cgi?id=56474 Priority: medium Bug ID: 56474 Assignee: nouveau at lists.freedesktop.org Summary: 3D app segfaults on NV46 Severity: normal Classification: Unclassified OS: Linux (All) Reporter: 1o5g4r8o at gmail.com Hardware: x86 (IA32) Status: NEW
2014 Feb 21
3
[PATCH 1/4] nv30: remove use_nv4x, it is identical to is_nv4x
Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- Perhaps there was a day when those were different, but that day is not today. src/gallium/drivers/nouveau/nv30/nv30_context.c | 1 - src/gallium/drivers/nouveau/nv30/nv30_context.h | 1 - src/gallium/drivers/nouveau/nv30/nvfx_fragprog.c | 20 ++++++++++---------- src/gallium/drivers/nouveau/nv30/nvfx_vertprog.c | 8 ++++---- 4
2014 Jun 17
0
[PATCH try 2 2/2] gallium/nouveau: move pushbuf and fences to context
...- return NULL; - } + if (ret) + goto err; /*XXX: make configurable with performance vs quality, these defaults * match the binary driver's defaults @@ -233,6 +287,14 @@ nv30_context_create(struct pipe_screen *pscreen, void *priv) if (debug_get_bool_option("NV30_SWTNL", FALSE)) nv30->draw_flags |= NV30_NEW_SWTNL; + nouveau_fence_new(&nv30->base.fence, &nv30->base.fence.current, FALSE); + + if (!screen->cur_ctx) { + nv30_screen_init_hwctx(screen, nv30->base.pushbuf); + screen->cur_ctx = nv30; + } + nouveau...
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
...if (ret) > + goto err; > > /*XXX: make configurable with performance vs quality, these defaults > * match the binary driver's defaults > @@ -233,6 +287,14 @@ nv30_context_create(struct pipe_screen *pscreen, void *priv) > if (debug_get_bool_option("NV30_SWTNL", FALSE)) > nv30->draw_flags |= NV30_NEW_SWTNL; > > + nouveau_fence_new(&nv30->base.fence, &nv30->base.fence.current, FALSE); > + > + if (!screen->cur_ctx) { > + nv30_screen_init_hwctx(screen, nv30->base.pushbuf); > + screen->...
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