Displaying 8 results from an estimated 8 matches similar to: "[PATCH 1/2] nv40: don't crash on empty fragment program"
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
2009 Dec 21
1
Clean up of nv40_context->state.hw and nv40_screen->state
Hi,
I'm trying to find a place where objects held in
nv40_context->state.hw[] and nv40_screen->state[] are being unreferenced
during pipe_context destruction.
Currently I'm observing that these objects are not unreferenced and
since they hold reference to buffer objects, the buffer objects
themselves are not unreferenced as well (for example color buffer or z
buffer).
In
2006 Jun 15
1
Backup Question?
This may be slightly off topic.
I am using FreePBX, and using it's backup feature.
Here is the question part:
I would like to copy my backup off the asterisk server.
>From your experiences, which approach seems more resilient to failure:
Push the backup from asterisk to another server using STFP or FTP?
Pull the backups from asterisk from another server using SFTP or other?
The
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
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
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