On Llu, 2004-05-17 at 04:10, David Bronaugh wrote: > Why not just be able to query how much physical video RAM is -not- > allocated? > > It sounds to me like this would solve the problem.
Lots of hardware has quite complex policy rules for the layout of specific objects. Nor is unallocated ram sufficient info in the simple case as you don't know how it is fragmented. You need a simple memory manager in kernel space for the video ram, with a little bit of policy in the per card layer. The code all exists in the sis fb driver (the code in the sis dri that seems to do it is broken though) Some hardware also has textures and video split. Some of it has AGP fallback for buffers, or even main memory linear buffers. Take a not atypial card - the sis6326 Frame buffer within the low 4Mb Z buffer within the low 4Mb or AGP or main memory Xv buffers in the low 4Mb Textures in main memory, agp or any of 8Mb but all parts must be in the same type of RAM Managing that properly is quite complex (and neither X nor DRI currently come close). ------------------------------------------------------- This SF.Net email is sponsored by: SourceForge.net Broadband Sign-up now for SourceForge Broadband and get the fastest 6.0/768 connection for only $19.95/mo for the first 3 months! http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
