Re: [Mesa3d-dev] gallium (was Re: radeon r6xx DRM...)

2008-06-04 Thread Zack Rusin
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

Re: [Mesa3d-dev] gallium (was Re: radeon r6xx DRM...)

2008-06-04 Thread Dave Airlie
> > 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 t

[Mesa3d-dev] gallium (was Re: radeon r6xx DRM...)

2008-06-04 Thread Brian Paul
Dave Airlie wrote: > Stephane wrote: >> Hi Brian, >> >> It seems like people are mostly concerned about gallium stability >> right now. How stable wioll the interfaces be in the future ? Maybe if >> you could tell us, that'd help others jump in. The gallium interfaces won't change radically, but

[Mesa3d-dev] [PATCH] autoconf: Check for posix_memalign

2008-06-04 Thread Dan Nicholson
Rather than just defining HAVE_POSIX_MEMALIGN on Linux, check whether the function exists on all platforms and define the macro if it is. --- Dan This seems like the right thing to do, but I only have Linux to test on. Any BSDers know if this is alright? As I understand it, posix_memalign is av