On Wed, Oct 02, 2002 at 04:35:16PM -0600, Jens Owen wrote: > Ian Romanick wrote: > > > Really there are 3 places the texture data can be duplicated: in the app, in > > libGL, and on-card / AGP. This can either be done by exposing some sort of > > "allocate AGP memory" extension or with APPLE_client_storage and dynamic AGP > > remapping. > > > > I've done a cursory look at the AGP driver, and it seems like this is > > possible, but I'm not positive. Anyone know for sure? It is definitly > > possible in the AGP spec because Mac OS X can do it. :) > > I believe the R200 implementation of APPLE_client_storage allocates > space from a static pool in AGP space.
I don't think that's quite right. If I'm not mistaken, the R200 driver exports a GLX extension to allocate memory from AGP space and that memory can be used with A_cs. > Are you looking for a way to > make the AGP pool larger and dynamically move pages in and out of the > AGP aperature? On Mac OS X (from 10.1 on, I believe), the OS can map any memory page into the AGP aperture at any time. The idea behind A_cs is that people malloc space for a texture, specify GL_UNPACK_CLIENT_STORAGE_APPLE to glPixelStorei, then call glTexImage?D with their pointer. The GL driver then keeps the pointer (instead of copying the data) and, when the texture is needed, maps the memory into AGP space. This way you really do only have one copy of the texture in memory. I guess the short answer to your question is "yes." :) -- Smile! http://antwrp.gsfc.nasa.gov/apod/ap990315.html ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
