Jerome Glisse wrote: > Hi Keith, > > I have been laging behind on gallium3d winsys change so i discover today > that winsys surface data access functions have been removed from winsys. > So i was wondering how do you think to replace them ? I believe they are > needed so for instance when we use failover the softpipe driver can access > texture which are stored in native hw format (tiled, compressed or > anyothers > storage scheme specific to the target hw) and so we can avoid having > copy of > texture just for softpipe (btw such things would need some change to > failover > i think).
Hey Jerome, I'm impressed that you got failover working at all - it was pretty much in a 'conceptual' state - nobody's ever tried to use it... It sounds like the functions you're talking about are the get/put_tile() interfaces? Out of interest, what fallback conditions are you catching? Although we do have the failover module, for most hardware the approach has been to try and use the state tracker, the draw module, and/or shader techniques to avoid fallbacks altoghether... I would have guessed that for hardware of the r300+ era, that should be sufficient to cover almost everything of importance. What are the issues you're dealing with in particular? Keith ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Mesa3d-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
