Displaying 14 results from an estimated 14 matches similar to: "[PATCH] Add missing include"
2009 Dec 21
2
[PATCH 1/2] Unreference state/buffer objects on context/screen destruction
- unreference state objects so that buffer objects are unreferenced and
eventually destroyed
- free channel at screen's destruction
Index: nv50/nv50_screen.c
===================================================================
--- nv50/nv50_screen.c (wersja 32083)
+++ nv50/nv50_screen.c (kopia robocza)
@@ -162,7 +162,22 @@
nv50_screen_destroy(struct pipe_screen *pscreen)
{
struct
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
2012 May 12
7
[Patches] mesa/nv30: Diverse set of patches that improve NV3x render quality V2
A reworked version of 3 out of 4 patches mentioned earlier.
[1/4]: Fixes nearly all piglit vertprog testcases, due to now being able to pass the results on to the fragment shader. V2: rename samplers to texcoords.
[2/4]: Fixes shader compiler assertion errors, as some source registers do not exist for certain operations. Fixes several piglit tests when mesa is compiled with --enable-debug
[3/4]:
2015 May 26
2
[PATCH 2/2] nv30/draw: switch varying hookup logic to know about texcoords
On 25.05.2015 21:29, Ilia Mirkin wrote:
> Commit 8acaf862dfe switched things over to use TEXCOORD instead of
> GENERIC, but did not update the nv30 swtnl draw paths. This teaches the
> draw logic about TEXCOORD.
>
> Among other things, this fixes a crash in demos/arbocclude when using
> swtnl. Curiously enough, the point-sprite piglit works without this.
>
> Signed-off-by:
2015 May 26
2
[PATCH 2/2] nv30/draw: switch varying hookup logic to know about texcoords
On 26.05.2015 02:49, Ilia Mirkin wrote:
> On Mon, May 25, 2015 at 8:37 PM, Tobias Klausmann
> <tobias.johannes.klausmann at mni.thm.de> wrote:
>>
>> On 25.05.2015 21:29, Ilia Mirkin wrote:
>>> Commit 8acaf862dfe switched things over to use TEXCOORD instead of
>>> GENERIC, but did not update the nv30 swtnl draw paths. This teaches the
>>> draw
2009 Jun 24
0
[PATCH] nv50: fix previous patches
This fixes the previous patches, and add some debugging output
if NV50_PROGRAM_DUMP is un-commented.
Will merge this into the patches, later.
---
src/gallium/drivers/nv50/nv50_program.c | 94 +++++++++++++++++++------------
1 files changed, 58 insertions(+), 36 deletions(-)
diff --git a/src/gallium/drivers/nv50/nv50_program.c b/src/gallium/drivers/nv50/nv50_program.c
index 4b05075..caf03c9
[Bug 59242] New: some mesa demos start to segfault after "nouveau: improve buffer transfers" on nv43
2013 Jan 11
2
[Bug 59242] New: some mesa demos start to segfault after "nouveau: improve buffer transfers" on nv43
https://bugs.freedesktop.org/show_bug.cgi?id=59242
Priority: medium
Bug ID: 59242
Assignee: nouveau at lists.freedesktop.org
Summary: some mesa demos start to segfault after "nouveau:
improve buffer transfers" on nv43
Severity: normal
Classification: Unclassified
OS: Linux (All)
2008 Nov 11
2
Memory corruption on Gallium window resize, diagnosed?
Hi,
I've been playing with nouveau/mesa branch gallium-0.1, trying to get
trivial/tri working on nv20 (with nv10 code). When ever I resize the window,
it ends up in an assert failure:
#0 0xf790744f in _debug_assert_fail (expr=0xf791908f "0", file=0xf7919050 "nv20_state_emit.c", line=139,
function=0xf7919034 "nv20_state_emit_framebuffer") at p_debug.c:335
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
2010 Jan 18
0
[PATCH] nv04-nv40: Rewrite and unify miptree and transfer code
This patch rewrites all the miptree layout and transfer code in the
pre-NV50 Gallium drivers.
The code is also unified among them and put in the nv04 directory.
The current code is broken in several ways:
1. 3D textures are laid out first by face, then by level, which is
incorrect
2. Cube maps should have 128-byte aligned faces
3. Swizzled textures have a strange alignment test that seems
2010 Jan 18
0
[PATCH] nv04-nv40: Rewrite and unify miptree and transfer code (v2)
Changes:
- Fixed some nv##_miptree that were not converted to nv04_miptree.
- Disable swizzling on non-RGBA 2D textures, since the current 2D
code is mostly broken in those cases. A later patch will fix this.
Thanks to Andrew Randrianasulu who reported this.
This patch rewrites all the miptree layout and transfer code in the
pre-NV50 Gallium drivers.
The code is also unified among them and
2009 May 06
2
nv50: shader generation patches
Hi ! I've been trying to improve NV50 shader generation a bit the last couple of weeks, so here is
what I've produced. I don't know if it's usable for you or just a pile of horrible hacks, but at
least it makes some mesa demos render more correcly, p.e. the teapot (aside from mip-mapping issues
of the floor texture), arbfplight, and I think the gears also didn't appear as they
2009 Dec 30
4
[PATCH 1/3] nv50: remove vtxbuf stateobject after a referenced vtxbuf is mapped
- This avoids problematic "reloc'ed while mapped" messages and
some associated corruption as well.
Signed-off-by: Maarten Maathuis <madman2003 at gmail.com>
---
src/gallium/drivers/nouveau/nouveau_screen.c | 21 +++++++++++++++++++++
src/gallium/drivers/nouveau/nouveau_screen.h | 3 +++
src/gallium/drivers/nouveau/nouveau_stateobj.h | 13 +++++++++++++
2017 Aug 21
20
[Bug 102349] New: nv4x crashing with plasmashell - gdb log included
https://bugs.freedesktop.org/show_bug.cgi?id=102349
Bug ID: 102349
Summary: nv4x crashing with plasmashell - gdb log included
Product: xorg
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: blocker
Priority: medium
Component: Driver/nouveau