On Wed, 2010-02-03 at 07:38 -0800, Kristian Høgsberg wrote: > On Wed, Feb 3, 2010 at 10:31 AM, Keith Whitwell <kei...@vmware.com> wrote: > > Historically we had a lot of helpers in gallium/include, which have been > > incrementally moved out to gallium/auxiliary. > > Is there a way we can structure the code so that the atomic operations > can be made available for core mesa (I guess I'm talking about the GL > state tracker/implementation, either way, stuff like struct > gl_framebuffer refcounts etc).?
A lot of the aux code in mesa/src/gallium does not specifically relate to gallium and more generally provides os/system abstractions that would be useful to Mesa. To date, Mesa's interactions with the gallium codebase have been strictly limited to the mesa state tracker. For the purposes of rendering, I think this makes sense. However, there's preventing us from factoring out the os-abstraction parts of gallium (separate from anything to do with 3d, graphics or rendering) and making them available to Mesa, which has many similar requirements. I'd be in favor of this anyway as it would help untangle the various different things being achieved in the gallium/aux directory. Keith ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
