On Thu, Mar 27, 2003 at 03:06:03AM +0100, Michel Dänzer wrote: > On Don, 2003-03-27 at 00:37, Keith Whitwell wrote: > > Ian Romanick wrote: > > > Michel Dänzer wrote: > > > > > >> On Mit, 2003-03-26 at 21:22, Ian Romanick wrote: > > >> > > >>> If the paged memory system is only used when DRI is enabled, does it > > >>> really matter where the code the X server calls is located? Could we > > >>> make the memory manager some sort of API-registered callback? It > > >>> would be one that only DRI (and perhaps video-capture extensions) > > >>> would ever use, but still. > > >> > > >> > > >> > > >> As far as I understand Mark Vojkovich's comments on the next generation > > >> XAA, all offscreen memory management is going to be handled via driver > > >> callbacks. > > > > > > > > > Interesting. What about "on screen?" I mean, are there any plans to > > > re-size the amount of memory used for the front buffer when the screen > > > mode changes? > > > > > > > Isn't that the RandR proposal, promoted or developed by core team X-iles? > > I'd say it's slightly more than a proposal, as the resize part is > implemented in 4.3.0. :) I do think dynamic management of everything > including the front buffer is the long term goal.
I don't believe it frees (do you say that in english ?) the Onscreen memeory though, i had the impression that it just allocate memory for the maximum possible screen and use a part of it if you are using a lesser resolution, a bit like the virtual memory is used right now. Friendly, Sven Luther ------------------------------------------------------- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
