similar to: [Bug 93373] New: sometimes hickup with persistent garbaby

Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- src/gallium/drivers/nouveau/nouveau_buffer.c | 4 +--- src/gallium/drivers/nouveau/nouveau_context.h | 1 - 2 files changed, 1 insertion(+), 4 deletions(-) diff --git a/src/gallium/drivers/nouveau/nouveau_buffer.c b/src/gallium/drivers/nouveau/nouveau_buffer.c index e308ff4..904e2cc 100644 ---

Signed-off-by: Ilia Mirkin <imirkin at alum.mit.edu> --- src/gallium/drivers/nouveau/nv50/nv50_context.c | 22 ++++++++++++++++++- src/gallium/drivers/nouveau/nv50/nv50_context.h | 1 + src/gallium/drivers/nouveau/nv50/nv50_vbo.c | 29 ++++++++++++++++++++++++- 3 files changed, 50 insertions(+), 2 deletions(-) diff --git a/src/gallium/drivers/nouveau/nv50/nv50_context.c

The main patches are from Christoph. Unfortunately they're a little beyond my understanding of all the vertex-related details, but they generally seemed fine. I'm just going to push these unless someone steps up to review them. Christoph Bumiller (2): nvc0: add support for indirect drawing nvc0: fix translate path for PRIM_RESTART_WITH_DRAW_ARRAYS Ilia Mirkin (1): nouveau: check if

Hello, I got trouble installing tinc daemon. Every time when a connection comes in, the daemon crashes: Mar 6 18:32:56 localhost tinc.vpn[20703]: tincd 1.0pre3 (Feb 21 2001 02:32:50) starting, debug level 5 Mar 6 18:32:56 localhost tinc.vpn[20703]: Ready: listening on port 655 Mar 6 18:33:00 localhost tinc.vpn[20703]: Connection from 192.168.0.4 port 1135 Mar 6 18:33:00 localhost

This is enough to enable tessellation support on nvc0. It seems to work a lot better on my GF108 than GK208. I suspect that there's some sort of scheduling shenanigans that need to be adjusted for kepler+. Or perhaps some shader header things. Even with the GF108, I still get occasional blue triangles in Heaven, but I get a *ton* of them on the GK208 -- seemingly the same issue, but it's

Hello, unfortunately I got some trouble using ext3 - the system hangs when working in a certain directory. Not completely, I can switch between consoles and reboot with SysRQ, but cannot do anything which requires disk IO: not start any applications, not umount, nothing. I could send the strace output, but I don't think this would help anyone. Sorry, but I don't have a clue where to start

I went through the gallium-nine tree and picked out nouveau patches that are general bug-fixes. The first bunch I'd like to also get into 10.2. I've reviewed all of them and they make sense to me, but sending them out for public review as well in case there are any objections. Unless I hear objections, I'd like to push this by Friday. Christoph Bumiller (11): nv50,nvc0: always pull

Hello, I packaged the old ext3 patch for Debian, and now I would like to create a patch-package of the current version for kernel 2.4.9. I consider to include Theodore's ext2 and ext3 readdir speedup patches and modify the 0.9.9 patch as needed to apply it on kernel 2.4.9. Does anyone (except of me) use all this parts together and report them to be stable enough? Gruss/Regards, Eduard. --

Hello, recently Theodory Tso posted a patch for the ext2fs driver, which improves speed of find and similar programs. Background: the application access all entries in the directory in the order they are stored on the disk. The current ext2 (and apparently Ext3) run a lookup function for each readdir call, starting with the first node! Theodore stores a refference to the node which was accessed

Hello everybody, I have just released tinc 1.0pre4. Changes: - New authentication protocol (better security, and faster too). - TCPonly and IndirectData are back (but not fully tested). - Documentation revised, it's really up to date with the released package now. - tincd -K now stores public/private keys in PEM format, but keys of 1.0pre3 can still be used. - Faster and more secure

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

Hallo short question how is the Syntax for interactivity.patch ext3-dir-speedup.patch ? patch -p0 ext3-dir-speedup.patch doesnt work -- Frank

Hi, "Asterisk 1.8.10.0-1digium1~squeeze built by pbuilder @ nighthawk on a x86_64 running Linux on 2012-03-08 23:05:09 UTC" We have some problem when running a AGI script (build with PHP), existing channels (all of them) gets a "hickup" and then continues. We are using AGI to lookup incoming calls in directory. It is kinda annoying, and I don't understand how it can be

Why not fix the new names instead to be like the old names? Seems like that would be way simpler... On Feb 15, 2016 12:38 AM, "Ben Skeggs" <skeggsb at gmail.com> wrote: > From: Ben Skeggs <bskeggs at redhat.com> > > We've previously had identical naming between vertex and texture > formats, so it mostly made sense to define these together. > > However,

Please don't hate me ;-) Adibar --

I'm using Michel Fortin's MDTest cases to rewrite my html2text.php script. Just now I stumbled upon this bug (in PHP Markdown at least): # Input: Backtick: ``\``` # Output: <p>Backtick: ``&#96;``</p> # Should-Be Output: <p>Backtick: <code>`</code></p> If you (Michel) are already aware of this, just ignore me ;-) -- Milian Wolff

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

Hi all! I saw TODO comment in nv50_vbo.c and decided to look at similar file, nvc0_vbo.c. I copied those two lines into nv50 with slight name change (nvc0->nv50) and apparently it doesn't fix any OpenGL app I have, but does not broke them further (I have compute pacthes currently applied, so some breakage expected). diff --git a/src/gallium/drivers/nouveau/nv50/nv50_vbo.c

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 +-

A question regarding the “kerberos method” configuration option in smb.conf: Are there any practical differences between using ’secrets and keytab’ and ’system keytab’? I’ve been running Samba servers using both methods for a long time and both seems to work more or less fine, but since we’re having this “login hickup at 10 hour service ticket expiration problem” I’m trying to find out if this