Re: Sourceforge CVS, was Re: [Dri-devel] radeon error

2003-09-03 Thread José Fonseca
On Tue, Sep 02, 2003 at 06:21:32PM +0100, Keith Whitwell wrote: > Thomas Emmel wrote: > > > > >I would do so if I could download the source. > >CVS is currently unusable for normal users. > >Error is: > > > >cvs [server aborted]: cannot make directory KSC5601: No space left on > >device > > > >and

Re: Sourceforge CVS, was Re: [Dri-devel] radeon error

2003-09-03 Thread Morten Hustveit
> On Maw, 2003-09-02 at 19:42, Jon Smirl wrote: > > There are 31 people with write access to dri.sf.net. The simplest > > solution would be for those 31 to switch to BitKeeper. On Wednesday 03 September 2003 15:17, Alan Cox wrote: > Providing they don't have an employer or themselves work on anyth

Re: Sourceforge CVS, was Re: [Dri-devel] radeon error

2003-09-03 Thread Martin Spott
Larry McVoy <[EMAIL PROTECTED]> wrote: > On Wed, Sep 03, 2003 at 02:17:19PM +0100, Alan Cox wrote: >> On Maw, 2003-09-02 at 19:42, Jon Smirl wrote: >> > There are 31 people with write access to dri.sf.net. The simplest solution >> > would be for those 31 to switch to BitKeeper. > If thos 31 are O

Re: Sourceforge CVS, was Re: [Dri-devel] radeon error

2003-09-03 Thread Larry McVoy
On Wed, Sep 03, 2003 at 02:17:19PM +0100, Alan Cox wrote: > On Maw, 2003-09-02 at 19:42, Jon Smirl wrote: > > There are 31 people with write access to dri.sf.net. The simplest solution > > would be for those 31 to switch to BitKeeper. If thos 31 are OK with that then it's easy, we can do a BK to

Re: [Dri-devel] radeon error

2003-09-03 Thread Thomas Emmel
On Wed, 2003-09-03 at 15:31, Dieter Nützel wrote: > I can second that. > > Have you tried demos/stex3d e.g. move the window to the right side of your > desktop? > Yes I have now and it looks really similar. The ring is broken on several positions. But the object I see in my application is alway

Re: [Dri-devel] radeon error

2003-09-03 Thread Thomas Emmel
On Wed, 2003-09-03 at 15:12, Keith Whitwell wrote: > After looking at your png's, it's not so clear that we know the problem well > enough for you to go ahead with this, so don't worry about it at this point. > > Can you give me backtraces from the NO_TCL crash? > Program received signal SIGFPE,

Re: [Dri-devel] radeon error

2003-09-03 Thread Dieter Nützel
Am Mittwoch, 3. September 2003 15:11 schrieb Thomas Emmel: > On Wed, 2003-09-03 at 13:53, Keith Whitwell wrote: > > Hmm, after looking at your screenshots, this seems like a seperate, > > unrelated problem. > > > > What happens if you set the following environment variables: > > > > R200_NO_VTX

Re: Sourceforge CVS, was Re: [Dri-devel] radeon error

2003-09-03 Thread Alan Cox
On Maw, 2003-09-02 at 19:42, Jon Smirl wrote: > There are 31 people with write access to dri.sf.net. The simplest solution > would be for those 31 to switch to BitKeeper. Providing they don't have an employer or themselves work on anything which forbids them using it (eg a version control system)

Re: [Dri-devel] radeon error

2003-09-03 Thread Keith Whitwell
Thomas Emmel wrote: On Wed, 2003-09-03 at 13:53, Keith Whitwell wrote: Hmm, after looking at your screenshots, this seems like a seperate, unrelated problem. What happens if you set the following environment variables: R200_NO_VTXFMT=t R200_NO_TCL=t Keith R200_NO_VTXFMT=t does

Re: [Dri-devel] radeon error

2003-09-03 Thread Thomas Emmel
On Wed, 2003-09-03 at 13:53, Keith Whitwell wrote: > Hmm, after looking at your screenshots, this seems like a seperate, unrelated > problem. > > What happens if you set the following environment variables: > > R200_NO_VTXFMT=t > R200_NO_TCL=t > > Keith R200_NO_VTXFMT=t does nothin

Re: [Dri-devel] radeon error

2003-09-03 Thread Keith Whitwell
Thomas Emmel wrote: On Wed, 2003-09-03 at 11:12, Thomas Emmel wrote: Back to my problem... On Tue, 2003-09-02 at 17:24, Keith Whitwell wrote: Is it correct that your application is using 1-dimensional textures and vertex arrays? This is a little-exercised aspect of the driver, but it shouldn't

Re: [Dri-devel] radeon error

2003-09-03 Thread Keith Whitwell
Thomas Emmel wrote: On Wed, 2003-09-03 at 11:12, Thomas Emmel wrote: Back to my problem... On Tue, 2003-09-02 at 17:24, Keith Whitwell wrote: Is it correct that your application is using 1-dimensional textures and vertex arrays? This is a little-exercised aspect of the driver, but it shouldn't

Re: [Dri-devel] radeon error

2003-09-03 Thread Martin Spott
Keith Whitwell <[EMAIL PROTECTED]> wrote: > Martin Spott wrote: >> I'm running a quite up-to-date mirror in Germany - currently without public >> access, but we could change this. Though this mirror suffers from absence of >> the SF server too > What sort of a mirror, Martin? I did a daily

Re: [Dri-devel] radeon error

2003-09-03 Thread Keith Whitwell
Martin Spott wrote: Thomas Emmel <[EMAIL PROTECTED]> wrote: and this message means that the CVS-server is full. I think this was mentioned before two days ago. Some days before I had the problem that the download hangs in xc/xc/util/patch infinitely. Now I tried to download completely from scrat

Re: [Dri-devel] radeon error

2003-09-03 Thread Thomas Emmel
Back to my problem... On Tue, 2003-09-02 at 17:24, Keith Whitwell wrote: > Is it correct that your application is using 1-dimensional textures and vertex > arrays? This is a little-exercised aspect of the driver, but it shouldn't too > hard to fix up. I'll try and rig up something here that ex

Re: Sourceforge CVS, was Re: [Dri-devel] radeon error

2003-09-02 Thread Keith Whitwell
Ian Romanick wrote: Jon Smirl wrote: The BitKeeper people have said they would love to be the host for DRI/Mesa source. We would still leave bug tracking, web pages, etc at Sourceforge. Only the source code would move. I'm not 100% positive, but I believe that if this happens I will no longer

Re: Sourceforge CVS, was Re: [Dri-devel] radeon error

2003-09-02 Thread Jon Smirl
--- Keith Whitwell <[EMAIL PROTECTED]> wrote: > That said lots of people like it a lot & I'm pretty fed up with slow cvs > operations -- rtag for instance should be instantaneous, but takes 10-20 min Instantaneous with BK. > - > why? > > Keith > > = Jon Smirl [EMAIL PROTECTED]

Re: Sourceforge CVS, was Re: [Dri-devel] radeon error

2003-09-02 Thread Keith Whitwell
If we just want to get rid of sf.net, CVS on freedesktop.org would probably be a good place to go. Plus, then we could set up cvsup, which offers fast checkouts/updates for folks and repository mirroring for developers. That was my original thought/hope -- a better free cvs host. sf.net is tank

Re: Sourceforge CVS, was Re: [Dri-devel] radeon error

2003-09-02 Thread Eric Anholt
On Tue, 2003-09-02 at 10:37, Jon Smirl wrote: > The BitKeeper people have said they would love to be the host for DRI/Mesa > source. We would still leave bug tracking, web pages, etc at Sourceforge. Only > the source code would move. > > They host the master copy of the Linux source: > http://linu

Re: Sourceforge CVS, was Re: [Dri-devel] radeon error

2003-09-02 Thread Ian Romanick
Jon Smirl wrote: The BitKeeper people have said they would love to be the host for DRI/Mesa source. We would still leave bug tracking, web pages, etc at Sourceforge. Only the source code would move. I'm not 100% positive, but I believe that if this happens I will no longer be allowed to make cont

Re: Sourceforge CVS, was Re: [Dri-devel] radeon error

2003-09-02 Thread Adam K Kirchhoff
On Tue, 2 Sep 2003, Keith Whitwell wrote: > It sounds like it should be sophisticated enough to allow a transition where > sourceforge cvs continues to work and be updated, and accept updates of its > own. That is it *sounds* like we could have some developers using cvs, some > bitkeeper but hav

Re: Sourceforge CVS, was Re: [Dri-devel] radeon error

2003-09-02 Thread Jon Smirl
There are 31 people with write access to dri.sf.net. The simplest solution would be for those 31 to switch to BitKeeper. It is easy to then mirror a read-only copy of the Bitkeeper repository to Sourceforge CVS. The key controversial point in the BK licenses is that the license for the free version

Re: Sourceforge CVS, was Re: [Dri-devel] radeon error

2003-09-02 Thread Linus Torvalds
On Tue, 2 Sep 2003, Keith Whitwell wrote: > > It sounds like it should be sophisticated enough to allow a transition where > sourceforge cvs continues to work and be updated, and accept updates of its > own. I'm afraid that it isn't quite _that_ seamless. The BK -> CVS/SVN gateway is one-way

Re: Sourceforge CVS, was Re: [Dri-devel] radeon error

2003-09-02 Thread Keith Whitwell
Linus Torvalds wrote: On Tue, 2 Sep 2003, Jon Smirl wrote: Having used CVS and BitKeeper, BitKeeper is way better. I will just add a big "Amen, Brother!" to that. Yes, BitKeeper has license issues, and some people won't touch it. But there are CVS/SVN gateways for that, and the kernel people (w

Re: Sourceforge CVS, was Re: [Dri-devel] radeon error

2003-09-02 Thread Linus Torvalds
On Tue, 2 Sep 2003, Jon Smirl wrote: > > Having used CVS and BitKeeper, BitKeeper is way better. I will just add a big "Amen, Brother!" to that. Yes, BitKeeper has license issues, and some people won't touch it. But there are CVS/SVN gateways for that, and the kernel people (who I think tend to

Re: Sourceforge CVS, was Re: [Dri-devel] radeon error

2003-09-02 Thread Martin Spott
Jon Smirl <[EMAIL PROTECTED]> wrote: > The BitKeeper people have said they would love to be the host for DRI/Mesa > source. We would still leave bug tracking, web pages, etc at Sourceforge. Only > the source code would move. This reheats the discussion about a BK to CVS gateway. There is one for t

Re: [Dri-devel] radeon error

2003-09-02 Thread Martin Spott
Thomas Emmel <[EMAIL PROTECTED]> wrote: > and this message means that the CVS-server is full. > I think this was mentioned before two days ago. > Some days before I had the problem that the download hangs in > xc/xc/util/patch infinitely. Now I tried to download completely > from scratch without

Re: Sourceforge CVS, was Re: [Dri-devel] radeon error

2003-09-02 Thread Jon Smirl
The BitKeeper people have said they would love to be the host for DRI/Mesa source. We would still leave bug tracking, web pages, etc at Sourceforge. Only the source code would move. They host the master copy of the Linux source: http://linux.bkbits.net/ and I have a copy of Mesa there: http://mes

Sourceforge CVS, was Re: [Dri-devel] radeon error

2003-09-02 Thread Keith Whitwell
Thomas Emmel wrote: I would do so if I could download the source. CVS is currently unusable for normal users. Error is: cvs [server aborted]: cannot make directory KSC5601: No space left on device and this message means that the CVS-server is full. OK, this was supposed to have been fixed in Augus

Re: [Dri-devel] radeon error

2003-09-02 Thread Thomas Emmel
On Tue, 2003-09-02 at 17:24, Keith Whitwell wrote: > Thomas, > > Is it correct that your application is using 1-dimensional textures and vertex > arrays? This is a little-exercised aspect of the driver, but it shouldn't too > hard to fix up. I'll try and rig up something here that exercises th

Re: [Dri-devel] radeon error

2003-09-02 Thread Keith Whitwell
Thomas, Is it correct that your application is using 1-dimensional textures and vertex arrays? This is a little-exercised aspect of the driver, but it shouldn't too hard to fix up. I'll try and rig up something here that exercises the problem. In the meantime, what does the following patch do

Re: [Dri-devel] radeon error

2003-09-01 Thread Thomas Emmel
On Mon, 2003-09-01 at 16:28, Keith Whitwell wrote: > > r200_maos_arrays.c:298: emit_vector: Assertion `0' failed. > > and the spplication died. > Can you provide me a backtrace from gdb of the crash? This is part of the backtrace: #5 0x458e59b2 in __assert_fail () from /lib/libc.so.6 #6 0x4678f

Re: [Dri-devel] radeon error

2003-09-01 Thread Keith Whitwell
Thomas Emmel wrote: Hi together, recently I sended an email to Keith who directed me to this list. My application (ABAQUS, see below for details) crashes if I use your r200-dri-module. The particular error is: r200_maos_arrays.c:298: emit_vector: Assertion `0' failed. and the spplication died. Ah,