On Jan 5, 2008 8:35 AM, Roland Scheidegger <firstname.lastname@example.org
R. Aditya Kadambi wrote:Hmm that's not much debug output. Guess you'd need a version built for
> I get these debug messages at start on setting R200_DEBUG=tex. Same
> messages for the successful rendering and unsuccessful rendering!
> r200AllocTexObj( 0x802bf2800, 0x802ef0800 )
No this patch is for the kernel module. It is against the git drm, but
> Thanks. Looks like the patch is for drivers/dri/radeon/*. I thought
> the driver was drivers/dri/r200/*. Am I missing something here?
it should apply to the kernel drm as well probably (but obviously the
file will be in a different location then).
If the problem is what I think it is, going past a certain texture
> In the meantime, I will put in the debug flags and report back. Also
> I will try out the different sizes mentioned.
height * depth is what will trigger the problem.
I did a little bit more experimentation yesterday.
I increase the texture size in the r200 driver from 256 to 512.
(a)I was able to render a 512x512x32 succesfully. Then I tried 256x256x64. It rendered successfully.
(b) I restarted X and then rendered 256x256x256. Only "half" volume rendered successfully.
I tried (a) again and it was a success. That sequence always works.
(c) I tried 512x512x32. Successful. Then tried 512x512x16. Successful. Then tried 256x256x64. Successful.
I will experiment a bit more. It almost looks like graphics memory is not "cleaned up". But it is "cleaned up" when I go from 512x512x* to
I will report back on the sequences.