On Tue, 8 Feb 2005, Ben Skeggs wrote:
Hello Vladimir,
1) It does not appear to be R300 specific - why doesn't similar Radeon ioctl work ? Also, I would imagine that this would require a change in r300 driver to work, wouldn't it ?
No, I suspected that it wasn't r300 specific actually, all the code does is write to a scratch register. So perhaps I should've just hooked up a R300_* ioctl number to the radeon code.
The thing we can (and do) use radeon ioctls from within the driver. So we can just call the Radeon ioctls directly - no need for R300 version.
This did bite us in the past, and ,probably, still does because of the need for different "engine idle" sequence for R300.
2) I was able to play Quake for somewhat prolonged periods, I don't think this would have really worked if aging was truly broken, though, maybe, I am wrong on this one.
Would you have a test app that shows brokenness ? Perhaps something that uses a lot of textures once.
It only seems to occur after the reference counts for all the dma buffers hit zero. After that, no more r300AllocDmaRegion calls are successful.
AFAIK, r300AllocDMA region allocates one of a several predefined buffers (you can see them printed by r300_demo), so if you do not free them there is nothing more to allocate.
I could be completely off on this one though - I can't look at the actual code at the moment and might have confused functions.
With regard to vertex buffers - these are in framebuffer memory, not in AGP one on R200 hardware (at least this was my understanding).
best
Vladimir Dergachev
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click -- _______________________________________________ Dri-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dri-devel
