From: Felix <fx...@gm...> - 2003-09-29 22:09:09
|
Hello, I'd like to get some sort of merge schedule for the config branch. Actually I had planned to do it now after getting back from vacation. But José had reported a strange compiling error in expat.h on his snapshot build machine that isn't solved yet. I also fixed another build probem on linux just yesterday that I didn't notice before because I never did a cvs upgrade. :-/ I think once the snapshots work the merge could proceed. The branch has been working reliably on my box for quite some time with r100. Eric Anholt was so kind to test the branch on FreeBSD with r128 and mga IIRC, and Michel Dänzer on Linux (Mac) with r200. Otherwise I'm not sure how widely it was tested though, considering that there were no working snapshots and that noone noticed the linux build problems for at least 3 weeks. ;-) Comments? Best regards, Felix ------------ __\|/__ ___ ___ ------------------------- Felix ___\_e -_/___/ __\___/ __\_____ You can do anything, Kühling (_____\Ä/____/ /_____/ /________) just not everything fx...@gm... \___/ \___/ U at the same time. |
From: F. <jrf...@tu...> - 2003-09-29 23:26:54
|
Felix, On Tue, Sep 30, 2003 at 12:09:04AM +0200, Felix Kühling wrote: > Hello, > > I'd like to get some sort of merge schedule for the config branch. > Actually I had planned to do it now after getting back from vacation. > But José had reported a strange compiling error in expat.h on his > snapshot build machine that isn't solved yet. I also fixed another build > probem on linux just yesterday that I didn't notice before because I > never did a cvs upgrade. :-/ Funny you brought this up - I was exactly trying to sort those build problems. Appearently your latest commit fixed it. The thing is that I build the snapshots by mixing the XFree86 4.3.0 source tree, which it has expat included, but an OLD version of expat: which doesn't define "enum XML_Status", XML_STATUS_ERROR, or XML_STATUS_OK... So you still need to sort that out: either you ask XFree86 to upgrade expat, or you need to adapt xmlconfig.c to cope with the older expat version. Otherwise, when the config branch hits XFree86's people will have the same troubles building that I did. > I think once the snapshots work the merge could proceed. The branch has > been working reliably on my box for quite some time with r100. Eric > Anholt was so kind to test the branch on FreeBSD with r128 and mga IIRC, > and Michel Dänzer on Linux (Mac) with r200. Otherwise I'm not sure how > widely it was tested though, considering that there were no working > snapshots and that noone noticed the linux build problems for at least 3 > weeks. ;-) There haven't been any snapshots for longer than that! Anyway, I'm now building a snapshot. If it succeeds please do a public request for testing on the dri-users and dri-devel. José Fonseca |
From: Alan H. <al...@fa...> - 2003-09-29 23:48:14
|
On Tue, Sep 30, 2003 at 12:24:53AM +0100, Jos=E9 Fonseca wrote: > Felix, >=20 > On Tue, Sep 30, 2003 at 12:09:04AM +0200, Felix K=FChling wrote: > > Hello, > >=20 > > I'd like to get some sort of merge schedule for the config branch. > > Actually I had planned to do it now after getting back from vacation. > > But Jos=E9 had reported a strange compiling error in expat.h on his > > snapshot build machine that isn't solved yet. I also fixed another bu= ild > > probem on linux just yesterday that I didn't notice before because I > > never did a cvs upgrade. :-/ >=20 > Funny you brought this up - I was exactly trying to sort those build > problems. Appearently your latest commit fixed it. The thing is that I > build the snapshots by mixing the XFree86 4.3.0 source tree, which it > has expat included, but an OLD version of expat: which doesn't define > "enum XML_Status", XML_STATUS_ERROR, or XML_STATUS_OK... >=20 > So you still need to sort that out: either you ask XFree86 to upgrade > expat, or you need to adapt xmlconfig.c to cope with the older expat > version. Otherwise, when the config branch hits XFree86's people will > have the same troubles building that I did. I've upgraded the XFree86 CVS to include expat 1.95.6. Alan. |
From: Martin S. <Mar...@un...> - 2003-09-30 08:23:27
|
Jos? Fonseca <jrf...@tu...> wrote: > Anyway, I'm now building a snapshot. If it succeeds please do a public > request for testing on the dri-users and dri-devel. .... probably combined with a short list of common pitfalls ? Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -------------------------------------------------------------------------- |
From: F. <jrf...@tu...> - 2003-09-30 10:12:24
|
On Tue, Sep 30, 2003 at 12:24:53AM +0100, José Fonseca wrote: > Anyway, I'm now building a snapshot. If it succeeds please do a public > request for testing on the dri-users and dri-devel. Just to let you know that the config snapshots built without any incident. Regards, José Fonseca PS: For general information, the HEAD failed to build somehere in the SiS driver. And the s3virge seems to have the missing-newline-at-eof problem somewhere. |
From: Keith W. <ke...@tu...> - 2003-09-30 10:22:50
|
José Fonseca wrote: > On Tue, Sep 30, 2003 at 12:24:53AM +0100, José Fonseca wrote: > >>Anyway, I'm now building a snapshot. If it succeeds please do a public >>request for testing on the dri-users and dri-devel. > > > Just to let you know that the config snapshots built without any incident. > > Regards, > > José Fonseca > > PS: For general information, the HEAD failed to build somehere in the > SiS driver. And the s3virge seems to have the missing-newline-at-eof > problem somewhere. What is the status of the s3virge driver? If it's only half working and now not compiling, I think we should disable it. Keith |
From: F. <jrf...@tu...> - 2003-09-30 10:36:22
|
On Tue, Sep 30, 2003 at 11:16:54AM +0100, Keith Whitwell wrote: > José Fonseca wrote: > >On Tue, Sep 30, 2003 at 12:24:53AM +0100, José Fonseca wrote: > >PS: For general information, the HEAD failed to build somehere in the > >SiS driver. And the s3virge seems to have the missing-newline-at-eof > >problem somewhere. > > What is the status of the s3virge driver? If it's only half working and > now not compiling, I think we should disable it. I wasn't quite clear on that - the s3virge only lives on its own branch (s3virge-0-0-1-branch) so there is nothing to disable. IIRC its state is that it's missing some GL functionality, and I don't think the security issue was even touted. See http://dri.sourceforge.net/snapshots/bleeding-edge/README.s3virge for more info. Actually, after more cerfull inspection, it appears that the build problem with the s3virge is that the branch is getting too far behind to correctly build with the X 4.3.0 sources... Have to look deeper though. It would be nice to keep the old drivers available. We should start doing 3D SDKs for each major XFree86 version, so that as the infrastucture (DRM, Mesa) gets _source-wise_ incompatible, we can still build the old drivers which ware _binary-wise_ compatible with recent X versions. I know XFree86 has a driver SDK already. Does anybody have an idea whether we could extend it for 3D? José Fonseca |
From: Keith W. <ke...@tu...> - 2003-09-30 10:47:37
|
José Fonseca wrote: > On Tue, Sep 30, 2003 at 11:16:54AM +0100, Keith Whitwell wrote: > >>José Fonseca wrote: >> >>>On Tue, Sep 30, 2003 at 12:24:53AM +0100, José Fonseca wrote: >>>PS: For general information, the HEAD failed to build somehere in the >>>SiS driver. And the s3virge seems to have the missing-newline-at-eof >>>problem somewhere. >> >>What is the status of the s3virge driver? If it's only half working and >>now not compiling, I think we should disable it. > > > I wasn't quite clear on that - the s3virge only lives on its own branch (s3virge-0-0-1-branch) so > there is nothing to disable. OK, no worries then. ... > It would be nice to keep the old drivers available. We should start > doing 3D SDKs for each major XFree86 version, so that as the infrastucture > (DRM, Mesa) gets _source-wise_ incompatible, we can still build the old > drivers which ware _binary-wise_ compatible with recent X versions. I > know XFree86 has a driver SDK already. Does anybody have an idea whether > we could extend it for 3D? I think that there is a forwards compatibility (4.1 modules work with 4.3) but not vice versa. I agree it's a good goal. Keith |
From: Alex D. <ag...@ya...> - 2003-09-30 13:49:11
|
unless someone beats me to it, I was planning on messing with the virge driver at some point going forward. I got a hold of the Duoview info from the virge databook, so I'm planning to add support for dualhead and probably mergedfb. after that I'll mess with the 3D driver. (does anyone know if there are databooks for the 3D stuff available anywhere? I heard that S3 released the virge databooks without an NDA. Also I seem to recall an SDK being available...) There are quite a few things on my plate right now (textured video for radeon, genericisizing mergedfb, etc.) though so I'm not sure when I'll get to it. plus I need to pick up an old virge mx first. Alex --- Jos� Fonseca <jrf...@tu...> wrote: > On Tue, Sep 30, 2003 at 11:16:54AM +0100, Keith Whitwell wrote: > > Jos� Fonseca wrote: > > >On Tue, Sep 30, 2003 at 12:24:53AM +0100, Jos� Fonseca wrote: > > >PS: For general information, the HEAD failed to build somehere in > the > > >SiS driver. And the s3virge seems to have the > missing-newline-at-eof > > >problem somewhere. > > > > What is the status of the s3virge driver? If it's only half > working and > > now not compiling, I think we should disable it. > > I wasn't quite clear on that - the s3virge only lives on its own > branch (s3virge-0-0-1-branch) so > there is nothing to disable. IIRC > its state is that it's missing some GL functionality, and I don't > think > the security issue was even touted. See > http://dri.sourceforge.net/snapshots/bleeding-edge/README.s3virge for > more info. > > Actually, after more cerfull inspection, it appears that the build > problem with the > s3virge is that the branch is getting too far behind to correctly > build > with the X 4.3.0 sources... Have to look deeper though. > > It would be nice to keep the old drivers available. We should start > doing 3D SDKs for each major XFree86 version, so that as the > infrastucture > (DRM, Mesa) gets _source-wise_ incompatible, we can still build the > old > drivers which ware _binary-wise_ compatible with recent X versions. I > know XFree86 has a driver SDK already. Does anybody have an idea > whether > we could extend it for 3D? > > Jos� Fonseca > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Dri-devel mailing list > Dri...@li... > https://lists.sourceforge.net/lists/listinfo/dri-devel __________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com |
From: Felix <fx...@gm...> - 2003-09-30 10:59:50
|
José, Thanks for getting the config snapshots working again. I just downloaded the latest one for radeon (radeon-config-20030930-linux.i386.tar.bz2). I can't test it on my notebook now, I'll do that when I get home. I just noticed that xdriinfo is still missing. There is even a manpage you could include in the snapshot. :) And I saw lots of tdfx-config snapshots. They are not needed, the tdfx driver doesn't support configuration yet. Regards, Felix On Tue, 30 Sep 2003 11:10:25 +0100 José Fonseca <jrf...@tu...> wrote: > > On Tue, Sep 30, 2003 at 12:24:53AM +0100, José Fonseca wrote: > > Anyway, I'm now building a snapshot. If it succeeds please do a public > > request for testing on the dri-users and dri-devel. > > Just to let you know that the config snapshots built without any incident. > > Regards, > > José Fonseca > > PS: For general information, the HEAD failed to build somehere in the > SiS driver. And the s3virge seems to have the missing-newline-at-eof > problem somewhere. ------------ __\|/__ ___ ___ ------------------------- Felix ___\_e -_/___/ __\___/ __\_____ You can do anything, Kühling (_____\Ä/____/ /_____/ /________) just not everything fx...@gm... \___/ \___/ U at the same time. |
From: Felix <fx...@gm...> - 2003-09-30 11:06:58
|
On Tue, 30 Sep 2003 13:00:16 +0200 Felix Kühling <felix@trabant> wrote: > José, > > Thanks for getting the config snapshots working again. I just downloaded > the latest one for radeon (radeon-config-20030930-linux.i386.tar.bz2). I > can't test it on my notebook now, I'll do that when I get home. I just > noticed that xdriinfo is still missing. There is even a manpage you > could include in the snapshot. :) Forget that, I should have read README.config :-/. Still it would be nice to include xdriinfo in the snapshot. It's quite small, so there's no real need for a separate package. The install script has a mechanism to run a custom script in an extras-subdir that could install xdriinfo and a manpage to the appropriate places. > > And I saw lots of tdfx-config snapshots. They are not needed, the tdfx > driver doesn't support configuration yet. The same for i810 and i830. > > Regards, > Felix > ------------ __\|/__ ___ ___ ------------------------- Felix ___\_e -_/___/ __\___/ __\_____ You can do anything, Kühling (_____\Ä/____/ /_____/ /________) just not everything fx...@gm... \___/ \___/ U at the same time. |
From: F. <jrf...@tu...> - 2003-09-30 12:01:26
|
On Tue, Sep 30, 2003 at 01:06:58PM +0200, Felix Kühling wrote: > On Tue, 30 Sep 2003 13:00:16 +0200 > Felix Kühling <felix@trabant> wrote: > > > José, > > > > Thanks for getting the config snapshots working again. I just downloaded > > the latest one for radeon (radeon-config-20030930-linux.i386.tar.bz2). I > > can't test it on my notebook now, I'll do that when I get home. I just > > noticed that xdriinfo is still missing. There is even a manpage you > > could include in the snapshot. :) > > Forget that, I should have read README.config :-/. Still it would be > nice to include xdriinfo in the snapshot. It's quite small, so there's > no real need for a separate package. The install script has a mechanism > to run a custom script in an extras-subdir that could install xdriinfo > and a manpage to the appropriate places. I'd generally agree with you. The problem is automating that without breaking the other snapshots - it'll take some work plus the risk of breaking the snapshots - so I'm not inclined to doit myself. But if you care enough to download the scripts in http://dri.sourceforge.net/snapshots/scripts/ and make a patch to dripkg.sh (and possibly package.sh) to do what you say I'll gladly welcome it... > > > And I saw lots of tdfx-config snapshots. They are not needed, the > > tdfx driver doesn't support configuration yet. > > The same for i810 and i830. Ok. Deleted and disabled those. José Fonseca |