On Fri, Oct 10, 2003 at 12:24:56PM +0100, Keith Whitwell wrote: > > >>>Right. And certainly now with the new linear allocator the Xserver can > >>>manage the whole lot. > >> > >>Does the X server make any promises about preserving the contents of the > >>fb memory? EG, if there's a VT switch, will the contents be saved > >>somehow? > > > > > >No. No preservation is done. We need to invalidate everything. > > That's a problem, as the only way we can do things like accelerated > CopyTexSubImage() and single-copy textures is if the FB contents are > guarenteed to be preserved. That's (I believe) one of the goals of Ian's > in-kernel memory manager. O.k.
> The other is to organize some sort of fair sharing of texture memory > between competing contexts. I would guess that the X server memory manager > doesn't try to do this sort of thing? Not currently, but I guess it could be made to. Alan. ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
