[Dri-devel] memory leak (?)

2002-06-13 Thread Bret Towe
i recently switched over to the trunk of dri since tcl branch is pretty much no more and after switching over i seem to of found a rather nasty bug it might of been there before cause i never really did test the tcl branch as long as i was playing with the trunk today anyways after playing ut for

Re: [Dri-devel] Re: tuxkart, and bug reports..

2002-06-13 Thread Mike Mestnik
--- Alan Hourihane <[EMAIL PROTECTED]> wrote: > On Thu, Jun 13, 2002 at 09:38:48AM -0700, Linus Torvalds wrote: > > On a separate topic - have you guys thought about replacing the user > > mailing list with a real newsgroup? Yes, newsgroups are noisy as hell, but > > they are also fairly easy to b

[Dri-devel] BUG: Mach64 20020613 -- lock in gltestperf

2002-06-13 Thread David Willmore
So, I downloaded the newest mach64 code and installed it. After fighting with the drm not loading automatically, and the bit depth being too high *smack*, I got direct rendering working! :) ~250 fps on glxgears is spiffy-- beats ~60 without DRI. With that behind me, I decided to get brave. So,

[Dri-users] Re: [Dri-devel] Mach64 2D accel fixed!

2002-06-13 Thread Jonathan Morton
>The challenge with back and depth buffers is being able to allocate >additional space on the fly (when a window is resized for example). We >chose a static allocation method over shutting down the application >after it's already been running. If a good mechanism can be devised for >addressing t

Re: [Dri-devel] Re: tuxkart, and bug reports..

2002-06-13 Thread Keith Whitwell
Alan Hourihane wrote: > On Thu, Jun 13, 2002 at 04:20:47PM +0100, José Fonseca wrote: > >>On 2002.06.13 15:43 Alan Hourihane wrote: >> >>>... >>> >>>What would be great, is if someone assigned the bugs to relevant >>>developers. Once someone is assigned to the bug report, they get >>>emails whene

Re: [Dri-devel] Understanding the internals of a X11/OpenGL Based Program (Using 3D Direct Rendering)

2002-06-13 Thread Smitty
> > 1.) MK II: > > _ > > \ > > +-+ | > > | X11/OpenGL Based Application | | > > | (Using 3D Direct Rendering) | | > > +--

Re: [Dri-devel] tuxkart, and bug reports.. (David Willmore)

2002-06-13 Thread Smitty
Howzit? > I see that there is a very active development community and three big projects > in the works (radeon, radeon T&L, and mach64). Yes I've slowly realise that this is what goes on in the DRI project, a thought has been rattling around in my head of late of a simple list of who is workin

Re: [Dri-devel] Broken context sharing/copying

2002-06-13 Thread Brian Paul
I intend to look into this problem, probably over the weekend. I've got at least one test program of my own to exercise this. Agreed, we shouldn't crash. -Brian Jens Owen wrote: > Brian, do these tests look reasonable to you? We certainly shouldn't > crash the server, even if they are unreaso

Re: [Dri-devel] Broken context sharing/copying

2002-06-13 Thread Jens Owen
Brian, do these tests look reasonable to you? We certainly shouldn't crash the server, even if they are unreasonable. Joe, can your try with the DRI CVS trunk? Joe Krahn wrote: > > I am trying to draw to two windows using one context. > It works for Mesa, but gives severe artifacts with DRI. >

Re: [Dri-devel] Re: tuxkart, and bug reports..

2002-06-13 Thread José Fonseca
On 2002.06.13 17:38 Linus Torvalds wrote: > > You shouldn't try to make developers work in some specific way ... I wasn't. I was trying to avoid that a way which has shown just bad results so far was once more forced upon the developers, and at the same time suggesting what it seems (IMHO) the

Re: [Dri-devel] Re: tuxkart, and bug reports..

2002-06-13 Thread Dieter Nützel
On Thursday 13 June 2002 19:01, Alan Hourihane wrote: > On Thu, Jun 13, 2002 at 05:52:59PM +0100, José Fonseca wrote: > > On 2002.06.13 17:19 Alan Hourihane wrote: > > >... > > > > > >If Dieter is volunteering to go through it - then power to him... > > > > Alan, it's not as simple as that. Althou

Re: [Dri-devel] Re: tuxkart, and bug reports..

2002-06-13 Thread Alan Hourihane
On Thu, Jun 13, 2002 at 09:38:48AM -0700, Linus Torvalds wrote: > On a separate topic - have you guys thought about replacing the user > mailing list with a real newsgroup? Yes, newsgroups are noisy as hell, but > they are also fairly easy to browse through (especially with a scoring > newsreader,

Re: [Dri-devel] Re: tuxkart, and bug reports..

2002-06-13 Thread Alan Hourihane
On Thu, Jun 13, 2002 at 05:52:59PM +0100, José Fonseca wrote: > On 2002.06.13 17:19 Alan Hourihane wrote: > >... > > > >If Dieter is volunteering to go through it - then power to him... > > Alan, it's not as simple as that. Although it's very kind of him to > volunteer, we all must get to a cons

Re: [Dri-devel] Re: tuxkart, and bug reports..

2002-06-13 Thread José Fonseca
On 2002.06.13 17:19 Alan Hourihane wrote: > ... > > If Dieter is volunteering to go through it - then power to him... Alan, it's not as simple as that. Although it's very kind of him to volunteer, we all must get to a consensus before taking actions. Do you really think that that consensus exi

Re: [Dri-devel] Re: tuxkart, and bug reports..

2002-06-13 Thread Linus Torvalds
On Thu, 13 Jun 2002, José Fonseca wrote: > > A system such as bugzilla can address everyone's needs (including Keith's > and Jens'). The way to address the needs of Keith and Jens is probably to let them ignore the bug tracking, and have others (maybe the originator, maybe just somebody else) t

Re: [Dri-devel] Re: tuxkart, and bug reports..

2002-06-13 Thread Alan Hourihane
On Thu, Jun 13, 2002 at 04:49:57PM +0100, José Fonseca wrote: > On 2002.06.13 16:24 Alan Hourihane wrote: > >... > > > >What I'm afraid might happen with setting up something like bugzilla, > >is the much more severe maintenance of it. If that person where to > >walk away from the project, we're m

Re: [Dri-devel] Re: tuxkart, and bug reports..

2002-06-13 Thread Alan Hourihane
On Thu, Jun 13, 2002 at 05:05:05PM +0100, Keith Whitwell wrote: > Alan Hourihane wrote: > >On Thu, Jun 13, 2002 at 04:46:44PM +0100, Keith Whitwell wrote: > > > >>It's not that I'm being lazy when I say I don't want to use it. > >> > >>First of all, if someone has a bug they want me to fix, they s

Re: [Dri-devel] Re: tuxkart, and bug reports..

2002-06-13 Thread Keith Whitwell
Alan Hourihane wrote: > On Thu, Jun 13, 2002 at 04:46:44PM +0100, Keith Whitwell wrote: > >>It's not that I'm being lazy when I say I don't want to use it. >> >>First of all, if someone has a bug they want me to fix, they should stick >>around long enough to have an email conversation about it.

Re: [Dri-devel] Re: tuxkart, and bug reports..

2002-06-13 Thread Alan Hourihane
On Thu, Jun 13, 2002 at 04:46:44PM +0100, Keith Whitwell wrote: > It's not that I'm being lazy when I say I don't want to use it. > > First of all, if someone has a bug they want me to fix, they should stick > around long enough to have an email conversation about it. I'm doing free > work for

Re: [Dri-devel] Re: tuxkart, and bug reports..

2002-06-13 Thread Keith Whitwell
Leif Delgass wrote: > On Thu, 13 Jun 2002, Keith Whitwell wrote: > > >>Here's one: >> >>On the radeon, the first time a 3d window is created, there is some screen >>corruption. It's probably the 2d driver getting something wrong. >> >>Keith >> > > What sort of corruption? I'm curious because

Re: [Dri-devel] Re: tuxkart, and bug reports..

2002-06-13 Thread Leif Delgass
On Thu, 13 Jun 2002, Keith Whitwell wrote: > Here's one: > > On the radeon, the first time a 3d window is created, there is some screen > corruption. It's probably the 2d driver getting something wrong. > > Keith What sort of corruption? I'm curious because we have a similar problem with ma

Re: [Dri-devel] Re: tuxkart, and bug reports..

2002-06-13 Thread José Fonseca
On 2002.06.13 16:24 Alan Hourihane wrote: > ... > > What I'm afraid might happen with setting up something like bugzilla, > is the much more severe maintenance of it. If that person where to > walk away from the project, we're much more stuck that where we are > now with SF. O.k. I admit that the

Re: [Dri-devel] Re: tuxkart, and bug reports..

2002-06-13 Thread Dieter Nützel
On Thursday 13 June 2002 17:17, Alan Hourihane wrote: > On Thu, Jun 13, 2002 at 04:03:05PM +0100, Keith Whitwell wrote: > > Alan Hourihane wrote: > > >On Wed, Jun 12, 2002 at 11:13:40PM +0200, Dieter Nützel wrote: > > >>On Wednesday 12 June 2002 20:53, Alan Hourihane wrote: > > >>[-] > > >> > > >>

Re: [Dri-devel] Re: tuxkart, and bug reports..

2002-06-13 Thread Alan Hourihane
On Thu, Jun 13, 2002 at 04:20:47PM +0100, José Fonseca wrote: > On 2002.06.13 15:43 Alan Hourihane wrote: > >... > > > >What would be great, is if someone assigned the bugs to relevant > >developers. Once someone is assigned to the bug report, they get > >emails whenever it's updated. But that som

Re: [Dri-devel] Strange behavior of the TCL branch

2002-06-13 Thread Slava Polyakov
On June 13, 2002 07:06 am, Adam Duck wrote: > > "Slava" == Slava Polyakov <[EMAIL PROTECTED]> writes: > > Slava> I have an ATI Radeon LE (which is pretty much the same > Slava> card as the ATI Radeon DDR but only with 32megs of DDR > Slava> ram not 64). > > Slava> Specifically

Re: [Dri-devel] Re: tuxkart, and bug reports..

2002-06-13 Thread José Fonseca
On 2002.06.13 15:43 Alan Hourihane wrote: > ... > > What would be great, is if someone assigned the bugs to relevant > developers. Once someone is assigned to the bug report, they get > emails whenever it's updated. But that someone needs to know who > to charge with that bug report. > > Someone

Re: [Dri-devel] Re: tuxkart, and bug reports..

2002-06-13 Thread Alan Hourihane
On Thu, Jun 13, 2002 at 04:03:05PM +0100, Keith Whitwell wrote: > Alan Hourihane wrote: > >On Wed, Jun 12, 2002 at 11:13:40PM +0200, Dieter Nützel wrote: > > > >>On Wednesday 12 June 2002 20:53, Alan Hourihane wrote: > >>[-] > >> > >>>We really need to clean up the stuff on SF now. Probably about

Re: [Dri-devel] Re: tuxkart, and bug reports..

2002-06-13 Thread Keith Whitwell
Alan Hourihane wrote: > On Wed, Jun 12, 2002 at 11:13:40PM +0200, Dieter Nützel wrote: > >>On Wednesday 12 June 2002 20:53, Alan Hourihane wrote: >>[-] >> >>>We really need to clean up the stuff on SF now. Probably about 90% >>>don't even apply now, or should at least be re-tested. >>> >>Yes, let

Re: [Dri-devel] Re: tuxkart, and bug reports..

2002-06-13 Thread Keith Whitwell
Steven Paul Lilly wrote: > I thought I would add my vote to the whole debate about what to do with the > mailing lists and SFBT. I would like both lists to continue and for their > proper uses to be enforced. I am not a developer or even a power user. I > just like knowing what is going on with th

[Dri-devel] Re: tuxkart, and bug reports..

2002-06-13 Thread Alan Hourihane
On Wed, Jun 12, 2002 at 11:13:40PM +0200, Dieter Nützel wrote: > On Wednesday 12 June 2002 20:53, Alan Hourihane wrote: > [-] > > We really need to clean up the stuff on SF now. Probably about 90% > > don't even apply now, or should at least be re-tested. > > Yes, let's start with that. > There a

Re: [Dri-devel] Re: tuxkart, and bug reports..

2002-06-13 Thread Steven Paul Lilly
I thought I would add my vote to the whole debate about what to do with the mailing lists and SFBT. I would like both lists to continue and for their proper uses to be enforced. I am not a developer or even a power user. I just like knowing what is going on with the development. Having a clear def

Re: [Dri-devel] Default AGP mode

2002-06-13 Thread Jeff Hartmann
David S. Miller wrote: >From: "Mike A. Harris" <[EMAIL PROTECTED]> >Date: Wed, 12 Jun 2002 21:39:23 -0400 (EDT) > >Basically, someone has asked for me to default AGPMode to 4 in >our config file, which I thought was absolutely crazy. The claim >is that AGP defaulted to

Re: [Dri-devel] Re: [Dri-patches] [ dri-Patches-567160 ] Radeon lockups with to many cliprects.

2002-06-13 Thread Keith Whitwell
>> >> Can you check this is correct since the merge of the TCL branch, and >> post the patch to the list instead of the patch-manager? (which >> should also die, IMO). >> >> Keith > > > I've alredy posted new patch to dri-devel. If sending patches to > dri-devel is preffered method then you

Re: [Dri-devel] Re: tuxkart, and bug reports..

2002-06-13 Thread Keith Whitwell
> Sorry. > > The problem was not in the logic of operation but in in use of variable > 'i' in this loop. After this loop it's value was never greater than > RADEON_NR_SAREA_CLIPRECTS and this variable is used in other loop (the > one containing 'smaller' one). It's value after the loop should

Re: [Dri-devel] Re: tuxkart, and bug reports..

2002-06-13 Thread Jacek Rosik
Keith Whitwell wrote: > >> >> >> >> --- xc/lib/GL/mesa/src/drv/radeon/radeon_ioctl.cWed Jun 12 >> 19:03:59 2002 >> +++ ../build/dri/xc/lib/GL/mesa/src/drv/radeon/radeon_ioctl.cWed >> Jun 12 20:01:42 2002 >> @@ -8

Re: [Dri-devel] Re: [Dri-patches] [ dri-Patches-567160 ] Radeon lockups with to many cliprects.

2002-06-13 Thread Jacek Rosik
Keith Whitwell wrote: > [EMAIL PROTECTED] wrote: > >> Patches item #567160, was opened at 2002-06-11 02:58 >> You can respond by visiting: >> http://sourceforge.net/tracker/?func=detail&atid=300387&aid=567160&group_id=387 >> >> >> Category: None >> Group: None >> Status: Open >> Resolution: N

Re: [Dri-devel] Strange behavior of the TCL branch

2002-06-13 Thread Adam Duck
> "Slava" == Slava Polyakov <[EMAIL PROTECTED]> writes: Slava> I have an ATI Radeon LE (which is pretty much the same Slava> card as the ATI Radeon DDR but only with 32megs of DDR Slava> ram not 64). Slava> Specifically: Slava> Linux misato 2.4.19-pre10 #1 Tue Jun 4 04:4

Re: [Dri-devel] Default AGP mode

2002-06-13 Thread Mike A. Harris
On Thu, 13 Jun 2002, David S. Miller wrote: >Date: Thu, 13 Jun 2002 00:53:16 -0700 (PDT) >From: David S. Miller <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Cc: [EMAIL PROTECTED], [EMAIL PROTECTED] >Content-Type: Text/Plain; charset=us-ascii >Subject: Re: [Dri-devel] Default AGP mode > > From: "

Re: [Dri-devel] Default AGP mode

2002-06-13 Thread David S. Miller
From: "Mike A. Harris" <[EMAIL PROTECTED]> Date: Thu, 13 Jun 2002 02:58:53 -0400 (EDT) Ben LaHaise suggested tonigth to me on IRC that perhaps we could read the AGP mode from the BIOS and set that by default, and also keep blacklist/whitelists in the drivers/whatever to deal w

Re: [Dri-devel] Mach64 2D accel fixed!

2002-06-13 Thread José Fonseca
On 2002.06.13 08:05 Michael Thaler wrote: > ... > > I had a lot of work to do for my diploma thesis lately, so I did not > test the mach64-0-0-4 branch. But waht I read on the list lately > sounds promising. Is the mach64-0-0-4 branch in a useable state now so > that is worthwhile for a pure user

[Dri-devel] Texcache sharin', page flippin' sonuvagun

2002-06-13 Thread Keith Whitwell
Keith Whitwell wrote: > Leif Delgass wrote: > >> CVSROOT:/cvsroot/dri >> Module name:xc >> Repository:xc/xc/programs/Xserver/hw/xfree86/drivers/ati/ >> Changes by:[email protected]/06/12 20:48:11 >> >> Log message: >> Fixed and enbled 2D acceleration. Also ATIDRIInitB

Re: [Dri-devel] Re: tuxkart, and bug reports..

2002-06-13 Thread Keith Whitwell
> > > > --- xc/lib/GL/mesa/src/drv/radeon/radeon_ioctl.c Wed Jun 12 19:03:59 2002 > +++ ../build/dri/xc/lib/GL/mesa/src/drv/radeon/radeon_ioctl.c Wed Jun 12 20:01:42 >2002 > @@ -856,14 +856,14 @@ >clear.depth

Re: [Dri-devel] Mach64 2D accel fixed!

2002-06-13 Thread Michael Thaler
Hello! > That's great news, Leif! I used to test the Mach64-branch on my Sony Vaio which has a 8 MB ATI Rage Mobility. The mach64-0-0-3 branch worked fine for me and I was really happy because I got a frame rate of about 25-30 in UT and Q3. I had a lot of work to do for my diploma thesis lately