From: Levent Y. <mli...@ga...> - 2002-12-10 01:07:07
|
Philip Brown wrote: >On Sun, Dec 08, 2002 at 11:08:32PM +0200, Levent Yavas wrote: > > >>... >>at this point we have s3savage, nv, mga chipsets working. i think we >>should supply those chipsets xfree-4.2.0 2d display drivers in binary >>release. with this way, there is no such incompability. we are totally >>version independant (or totally 4.2.0 dependant, choose one :) because >>xfree version changes will not affect utah-glx development. we will >>simply give working set of libraries in binary release. >> >> > >ah. okay, I think I understand now. > >Well, if you (or anyone else who wants to provide a binary set for > their favourite platform), go for it. > > want to do that, go right ahead > > > >>i have another problem, i prepared 'latest-release' binaries for mga, >>s3savage, nv with following command: >>./configure --enable-nv --enable-mga --enable-s3savage --disable-i810 >>--disable-mach64 --disable-s3virge --disable-sis6326 --without-x86-asm >>--without-mmx-asm --without-3dnow-asm --prefix=/usr >> >>problem is, mga and s3savage drivers wasn't compiled. my binaries only >>have nv drivers, s3savage and mga will not work! >> >> > >oops. > >Well, maybe you want to take the "savage-works" tag, and add on just the >latest nv stuff in the nv directory, and if that works better, make a new >tag. Or recommend a better layout. >It's possible the "latest-release" tag needs to be adjusted for some files >for it to to work better. I'd love to have some suggestions! > > > > ok, i'll prepare seperate binary releases for every working chipset. i also put related 4.2.0 version of 2d driver into it. surely i cannot test mga and savage releases. i'll away for two weeks from my computer (have exams) after that, i will have enough time to do. |