On Wed, 2009-10-28 at 05:21 -0700, José Fonseca wrote: > On Tue, 2009-10-27 at 14:45 -0700, Younes Manton wrote: > > I'd just like to add that if other interfaces will exist in the future > > (I recall pipe_2d_context being floated at one time) and state > > trackers want to use them without initializing a pipe_context > > needlessly and want to reuse the rest of the DRM winsys then the > > relevent parts of this patch (or comparable changes) will need to be > > considered sooner or later regardless of whether or not > > pipe_video_context exists. > > Indeed. > > And it is not only the problem of the pipe_*_context creation. There is > the problem of the state tracker still reaching out parts of the winsys. > > I really think that a simple driver with a generic interface query as I > proposed in > > http://www.mail-archive.com/mesa3d-dev@lists.sourceforge.net/msg07818.html > > is the best, and we sorely need it, with the recent and welcomed > increase of pipe drivers and state trackers. > > I'll try to prototype this on a few state trackers and see how it goes.
In the meantime though, I think we're getting to a point where there's enough riding on the interfaces in gallium/include/pipe that we want to start being a bit more rigorous about updates to that directory. We're already often using feature branches for larger changes and reviews for important patches. Let's formalize that for changes that touch the Gallium interfaces in include/pipe. Additionally, I'm going to play the maintainer card at this point and ask that changes to the include/pipe directory on the master branch go through me, after review on Mesa-dev. Development on the rest of the tree I'm OK with as it stands, but I think we need a coherent process to guide the direction of interface change and growth. For my own part, I'll make sure that my personal changes to gallium/include follow the same process as above, and are properly reviewed on the list before pushing. Keith ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
