On Fri, Dec 05, 2003 at 09:06:33AM +0000, Keith Whitwell wrote: > Alan Hourihane wrote: > >On Thu, Dec 04, 2003 at 04:44:49PM -0700, Brian Paul wrote: > > > >>Alan Hourihane wrote: > >> > >>>On Thu, Dec 04, 2003 at 12:44:06AM +0000, Alan Hourihane wrote: > >>> > >>> > >>>>I've created a newmesa branch that I'll be updating the Imakefiles so > >>>>that we can use the new Mesa trunk code with XFree86. > >>>> > >>>>It's late in the UK now, but I've made a start and I'll start adding > >>>>the Imakefiles I've done tomorrow. > >>>> > >>>>Anyone want to help out - please check it out and start comitting :) > >>>> > >>>>newmesa-0-0-1-branch. > >>> > >>> > >>>O.k. I've made most of the changes now and the branch builds. > >>> > >>>Indirect GLX appears to work fine, and I've tested the radeon_dri.so > >>>module and it appears to work, but it's limping along with some segfaults > >>>the I'm chasing now. > >>> > >>>This obviously gives us Mesa 5.1 (OpenGL 1.4) capability now too. > >>> > >>>Just checkout the Mesa trunk and set MesaSrcDir in host.def, and off you > >>>go. > >>> > >>>Report any problems here. > >> > >>Good work, Alan! That probably wasn't a very pleasant task! :) > > > > > >Definately not. It's at times like these when your really hate Imakefiles, > >but they do make it more readable that some of the Makefiles that get > >generated, so I'm happy. > > > > > >>Though, I think Mesa's new directory organization will satisfy us for > >>a long time to come and this kind of re-org won't be needed again. > > > > > >Indeed. I think moving most of the main code to the main/ directory > >was a big help in this work I've done. It really helped isolate some > >of the Imakefile work. > > > > > >>Also, there's about 12 new OpenGL extensions in Mesa 5.1 which will > >>get us up to date with the OpenGL 1.5 specification. Actually, I'll > >>rev Mesa 5.1 to 6.0 before advertising OpenGL 1.5 functionality (to > >>continue Mesa's long-standing versioning scheme). > > > > > >Great. > > > >I'm not getting segfaults actually, I had a bad radeon ddx driver > >installed. > > > >I am hitting a few assertions though which cause the application to abort > >immediately with the radeon_dri.so module though. > > These might be my fault - I've just committed a fix to Mesa CVS to take > care of some failures I introduced on the displaylist path that would sho > > >I'm sure there's a few more Imakefile cleanups, but they'll only be minor. > > > >So I'm keen for others to start looking at the other DRI drivers, and the > >sooner the better. Then this work can be merged to the trunk and we can > >all start keeping the DRI drivers up-to-date in the Mesa CVS rather than > >the DRI. This will allow the DRI CVS to be purely used for DRI related > >infrastructure work. Phew! > > I'll look at at least the r200 and i830 drivers today.
Great. Thanks Keith. Alan. ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel