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.
Ah, I did not realise that we could (and do) just call the radeon ioctls.
They do get freed at the end of r300_run_vb_render. r300ReleaseDmaRegion is the function which calls the ioctl.
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).
r200EmitArrays (which does much that same as upload_vertex_buffer in r300_dri) uses the alloc/release dma calls to grab the regions.
Could someone with knowledge of r200_dri explain how vertex buffer uploads are put into framebuffer memory on r200? I had
just assumed that the driver told r200 of the address of the buffer acquired from AllocDma. I've mostly likely got something
very confused here.
Thanks, Ben Skeggs.
------------------------------------------------------- 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 Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
