GARTSize option not documented on radeon and other problems

Hi, sorry for the crossposting, I don't know who to address. I am experimenting the new CFS scheduler on Linux and tried to start multiple glxgears to see whether they are really running smooth and have evenly distributed framerate. At first I could only start two instances of glxgears but the

[Bug 10848] New: Invalid write in prog_statevars.c

http://bugs.freedesktop.org/show_bug.cgi?id=10848 Summary: Invalid write in prog_statevars.c Product: Mesa Version: CVS Platform: x86 (IA32) OS/Version: All Status: NEW Severity: normal Priority: medium

[Bug 10848] Invalid write in prog_statevars.c

http://bugs.freedesktop.org/show_bug.cgi?id=10848 --- Comment #1 from [EMAIL PROTECTED] 2007-05-03 11:33 PST --- Looks like the matrix state tokens in r300_vertprog.c position_invariant() were wrong. I'm checking in a fix in git. -- Configure bugmail:

[Bug 10848] Invalid write in prog_statevars.c

http://bugs.freedesktop.org/show_bug.cgi?id=10848 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

Re: [RFC] [PATCH] DRM TTM Memory Manager patch

On Thu, 2007-05-03 at 01:01 +0200, Thomas Hellström wrote: It might be possible to find schemes that work around this. One way could possibly be to have a buffer mapping -and validate order for shared buffers. If mapping never blocks on anything other than the fence, then there isn't any

Re: GARTSize option not documented on radeon and other problems

On 5/3/07, Zoltan Boszormenyi [EMAIL PROTECTED] wrote: Hi, sorry for the crossposting, I don't know who to address. I am experimenting the new CFS scheduler on Linux and tried to start multiple glxgears to see whether they are really running smooth and have evenly distributed framerate.