On Thursday 05 June 2008 12:47:07 am Dave Airlie wrote: > > Gallium might ultimately wind up in its own repository as a stand-alone > > project. Afterall, Gallium drivers could be used by APIs other than > > OpenGL. > > The question is mainly from a distro point of view what do we need to ship > a gallium driver. The current method would mean we need a Mesa tree for > normal DRI drivers and a gallium-mesa tree for gallium based drivers. This > isn't brutal but I'd hate to spend a lot of time on the setup phase just > to find the target moved. > > So if gallium is in a separate project will it need parts of Mesa to > build.
No it won't. Gallium doesn't depend on Mesa at all. In a gross simplification Gallium is simply an interface that can be seen as the communication protocol between the API and the driver. For Mesa that API is OpenGL, so Mesa implements a Gallium state-tracker and that's it. Gallium shouldn't care whether it's Mesa or Bobs-Api that's running on top of it. (currently winsys kinda has a fixed dependency on state-trackers but we're working on fixing that). > Will the gallium/mesa interface move. The changes to the api when it comes software can be taken for granted, it's the "how frequent" that matters. Having said that we certainly want to keep Gallium interface stable for a long time. z ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
