Displaying 10 results from an estimated 10 matches for "deadwood".
2009 Dec 17
1
Question about nv40_draw_array
...h rather peculiar memory allocation/access
problem with call lists and I would like to ask for help in
understanding how a certain thing is implemented.
Let's assume I have a following call trace:
#0 0x985a764d in nv40_draw_arrays (pipe=0x988ba0fc, mode=5, start=0,
count=3)
at
/data/deadwood/AROS/AROS/contrib/gfx/libs/mesa/src/mesa/../gallium/drivers/nv40/nv40_vbo.c:192
#1 0x9865e773 in st_draw_vbo (ctx=0x9a163788, arrays=0x9a19384c,
prims=0x9a1d595c, nr_prims=23, ib=0x0,
index_bounds_valid=1 '\001', min_index=0, max_index=574)
at
/data/deadwood/AROS/AROS/contrib/g...
2003 Feb 19
4
Block Coding Pattern
Hi,
There seem to be 2 sets of block coding patterns in the
VP3x/Theora algorithm. Based on the comments in the code, the first
pattern is used if encoder version < 6 and the second pattern is used in
encoder version >= 6. None of the code to support the second pattern is
ever called. Is there an encoder with a version >= 6?
The code in question is
2004 Dec 07
1
smbd reads entire directory when creating files?
...ian
smb.conf is attached. Not much interesting in there, it is pretty much
stock. "vfs_ownerwrite" is a small VFS module I hacked up to do an
extra chown on a file that is written to the share (used in a common
PDC/Unix environment on some shared directories.) I am using the
"deadwood_ftp" share in this case, so the module is not involved.
-m
-------------- next part --------------
# Samba configuration file for media servers.
# -----
#
# $Id: smb.conf,v 1.2.4.6 2002/03/13 18:56:16 peloy Exp $
#
# This is the main Samba configuration file. You should read the
# smb.conf(5)...
2009 Feb 18
1
asterisk-users Digest, Vol 55, Issue 52
But clients can call to your IVR and do the payment from their home or the mobile, correct?
If that is possible, how they pay $50.53? I mean, how they enter the 0.53$? They use the * to express the (.)?
2010 Jan 04
1
NV_PFIFO_INTR_DMA_PUSHER
Hello,
Could someone briefly describe (or point me to the documentation) what
can be a reason for getting NV_PFIFO_INTR_DMA_PUSHER status
(nouveau_fifo_irq_handler).
This started happening immediately after I set the nouveau_vram_pushbuf
flag to TRUE ,it's 100% repetitive and causes fences not to be signaled.
Below is the debug log from moment of creation of fifo 1 to some point
in time
2008 Aug 11
2
problems with sieve and lda
Okay, after reading the wiki and list archives, I am confused.
I am attemping to get the deliver LDA working on a centos 5.1 system
# rpm -qa | grep dovecot
dovecot-1.0.7-2.el5
dovecot-sieve-1.0.2-6.el5
# rpm -qa | grep postfix
postfix-2.3.3-2
so that I can use Sieve for mail filtering to imap folders, I am using the
mbox format
Following the wiki here for system users
2003 Feb 23
6
More Missing Pieces
Hi,
I am making good progress on understanding, documenting, and
re-implementing VP3. I have found some more deadwood in the decoder code
and I just wanted to verify that it really has no place:
* Version 3.3 tables: There are 2 sets of VLCs: One for v3.1 and one for
v3.3. The v3.1 set is always selected. Are the v3.3 tables in production,
or will they ever be?
* DC Search Points: VP3 seems determined to predict...
2013 Jul 31
29
[PATCH 0/9] tools: remove or disable old/useless/unused/unmainted stuff
depends on "autoconf: regenerate configure scripts with 4.4 version"
This series removes some of the really old deadwood from the tools build
and makes some other things which are on their way out configurable at
build time with a default depending on how far down the slope I judge
them to be.
* nuke in tree copy of libaio
* nuke obsolete tools: xsview, miniterm, lomount & sv
* make xend optional, still on by de...
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
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