On Sunday 16 September 2007 02:41:24 pm Keith Whitwell wrote: > 1) Fewer state objects, probably 5 or 6. > 2) The constant state object life cycle, ie: > - CreateBlendState > - BindBlendState > - DestroyBlendState > 3) State partitioned in a hopefully sensible way for hardware. > > The intended usage will be that the driver's CreateBlendState function > is the only place you have to think about Mesa state, ie the driver does > a one-time-only conversion to hardware format state. > > In BindBlendState(), the driver only has to directly emit the > pre-computed values to registers.
I just pushed the start of those changes to gallium-0.1 branch. Our gallium i915 driver hasn't been ported to those changes quite yet (it compiles, but it doesn't use the new semantics). Still to do are the conversion of the shader state to immutable state object and work on the sample driver. z ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
