Re: [Dri-devel] Torque Engine causes machine lockup on radeon mobilityM7

2003-06-24 Thread Keith Whitwell
Zik Saleeba wrote: I'm still trying to track down the cause of the Torque Engine radeon crash. I've instrumented the calls Torque makes to gl so I can work out what's happening when it dies. The sequence of gl calls from the frame where it crashes can be downloaded at: http://www.zikzak.net/~zik/cr

Re: [Dri-devel] Torque Engine causes machine lockup on radeon mobility M7

2003-06-24 Thread Zik Saleeba
I'm still trying to track down the cause of the Torque Engine radeon crash. I've instrumented the calls Torque makes to gl so I can work out what's happening when it dies. The sequence of gl calls from the frame where it crashes can be downloaded at: http://www.zikzak.net/~zik/crash_frame.c.txt N

Re: [Dri-devel] Last part of GLX_SGI_make_current_read support

2003-06-24 Thread Brian Paul
Ian Romanick wrote: I'm rounding out the final bits of support for SGI_make_current_read. I've hit a (hopefully) minor snag, and I'd like some advice on how to proceede. At this point, *all* of the client-side support, both in libGL.so and in at least one driver, is in place. I'm now working o

[Dri-devel] Re: Only "normal" DRI and Mesa CVS access as developer, now?

2003-06-24 Thread Michel Dänzer
On Tue, 2003-06-24 at 21:53, Nicholas Wourms wrote: > Michel Dänzer wrote: > > On Tue, 2003-06-24 at 16:34, Keith Whitwell wrote: > [SNIP] > > > >>>To XFree86? Well, that's another question. > >> > >>That sounds more negative than I wanted. Basically, after the drivers are > >>living in Mesa cv

Re: [Dri-devel] Only "normal" DRI and Mesa CVS accessas developer, now?

2003-06-24 Thread Michel Dänzer
On Tue, 2003-06-24 at 21:19, José Fonseca wrote: > On Tue, Jun 24, 2003 at 08:44:32PM +0200, Michel Dänzer wrote: > > On Tue, 2003-06-24 at 17:37, José Fonseca wrote: > > > I mentioned XFree86.org because (supposedly) it has the bandwith and > > > machine resources to host the DRI repository, and o

[Dri-devel] Last part of GLX_SGI_make_current_read support

2003-06-24 Thread Ian Romanick
I'm rounding out the final bits of support for SGI_make_current_read. I've hit a (hopefully) minor snag, and I'd like some advice on how to proceede. At this point, *all* of the client-side support, both in libGL.so and in at least one driver, is in place. I'm now working on the server-side s

[Dri-devel] Re: Only "normal" DRI and Mesa CVS access as developer, now?

2003-06-24 Thread Nicholas Wourms
Michel Dänzer wrote: On Tue, 2003-06-24 at 16:34, Keith Whitwell wrote: [SNIP] To XFree86? Well, that's another question. That sounds more negative than I wanted. Basically, after the drivers are living in Mesa cvs, we could well end up just submitting patches to XFree86 for the rest - but tha

Re: [Dri-devel] Only "normal" DRI and Mesa CVS access as developer, now?

2003-06-24 Thread José Fonseca
On Tue, Jun 24, 2003 at 08:19:33PM +0100, José Fonseca wrote: > On Tue, Jun 24, 2003 at 08:44:32PM +0200, Michel Dänzer wrote: > > I wonder if it's really such a pressing problem though. > > Imagine you're working with somebody testing some code, but that person > has no CVS write access. After y

Re: [Dri-devel] Only "normal" DRI and Mesa CVS access as developer, now?

2003-06-24 Thread José Fonseca
On Tue, Jun 24, 2003 at 08:44:32PM +0200, Michel Dänzer wrote: > On Tue, 2003-06-24 at 17:37, José Fonseca wrote: > > I mentioned XFree86.org because (supposedly) it has the bandwith and > > machine resources to host the DRI repository, and obviously XFree86 and > > DRI are two very close entities.

Re: [Dri-devel] Savage-1_0_0-branch

2003-06-24 Thread Alex Deucher
CVS at sourceforge is using the backup server which has data that is 24+ hours old. I wasn't able to get it either. Alex --- Maximo <[EMAIL PROTECTED]> wrote: > At 09:13 AM 24/6/2003, you wrote: > >On Tue, Jun 24, 2003 at 06:00:57PM +0600, Dimitry N. Naldaev wrote: > > > В сообщении от 24 Июнь 2

Re: [Dri-devel] Savage-1_0_0-branch

2003-06-24 Thread Maximo
At 09:13 AM 24/6/2003, you wrote: On Tue, Jun 24, 2003 at 06:00:57PM +0600, Dimitry N. Naldaev wrote: > В сообщении от 24 Июнь 2003 15:19 Alan Hourihane написал: > > I'm still looking at the large differences in the 2D driver code, so I > > thought I'd ask if someone wanted to step up and fix the

Re: [Dri-devel] radeon drm in 2.5.73

2003-06-24 Thread Warren Turkal
On Tuesday 24 June 2003 07:07 am, Alexander Stohr wrote: > i am reading the list and i have not seen a fix for this. > maybe the root cause is somewhere else, > like using an uniprocessor config of an alternate CPU > or a non current CPU desing ( > if you hear about an answer, then please post to t

Re: [Dri-devel] Only "normal" DRI and Mesa CVS accessas developer, now?

2003-06-24 Thread Michel Dänzer
On Tue, 2003-06-24 at 16:34, Keith Whitwell wrote: > Keith Whitwell wrote: > > Michel Dänzer wrote: > > > >> On Mon, 2003-06-23 at 20:24, José Fonseca wrote: > >> > >>> On Mon, Jun 23, 2003 at 06:58:39PM +0200, Dieter Nützel wrote: > >>> > These sourceforge "backup" server move is very annoyi

Re: [Dri-devel] Only "normal" DRI and Mesa CVS accessas developer, now?

2003-06-24 Thread Michel Dänzer
On Tue, 2003-06-24 at 17:37, José Fonseca wrote: > On Tue, Jun 24, 2003 at 03:34:24PM +0100, Keith Whitwell wrote: > > Keith Whitwell wrote: > > >Michel Dänzer wrote: > > >>On Mon, 2003-06-23 at 20:24, José Fonseca wrote: > > >>>On Mon, Jun 23, 2003 at 06:58:39PM +0200, Dieter Nützel wrote: > > >>>

Re: [Dri-devel] radeon triangle fan hang

2003-06-24 Thread Michel Dänzer
On Tue, 2003-06-24 at 15:13, Keith Whitwell wrote: > Please try this diff - it may fix the problem in a lot of cases. Tried it with the r200 driver, bzflag caused a lockup pretty early on startup, with [drm:radeon_cp_cmdbuf] *ERROR* bad cmd_type 0 at 100f26f8 in the kernel output. I guess that m

Re: [Dri-devel] radeon triangle fan hang

2003-06-24 Thread Keith Whitwell
[EMAIL PROTECTED] wrote: On Tue, Jun 24, 2003 at 03:31:59PM +0100, Keith Whitwell wrote: [EMAIL PROTECTED] wrote: On Tue, Jun 24, 2003 at 02:13:17PM +0100, Keith Whitwell wrote: Please try this diff - it may fix the problem in a lot of cases. I'll try it later to see if I'm missing something

Re: [Dri-devel] Only "normal" DRI and Mesa CVS access as developer, now?

2003-06-24 Thread José Fonseca
On Tue, Jun 24, 2003 at 03:34:24PM +0100, Keith Whitwell wrote: > Keith Whitwell wrote: > >Michel Dänzer wrote: > >>On Mon, 2003-06-23 at 20:24, José Fonseca wrote: > >>>On Mon, Jun 23, 2003 at 06:58:39PM +0200, Dieter Nützel wrote: > These sourceforge "backup" server move is very annoying. It

Re: [Dri-devel] radeon triangle fan hang

2003-06-24 Thread leahcim
On Tue, Jun 24, 2003 at 03:31:59PM +0100, Keith Whitwell wrote: > [EMAIL PROTECTED] wrote: > >On Tue, Jun 24, 2003 at 02:13:17PM +0100, Keith Whitwell wrote: > > > >>Please try this diff - it may fix the problem in a lot of cases. > > > > > >I'll try it later to see if I'm missing something here, b

[Dri-devel] Local cvs repository of DRI

2003-06-24 Thread Dimitry N. Naldaev
Probably it is a good idia to have local cvs repository of DRI but how to keep it updated (ie sync it with main DRI repository on sf.org)? I probably not need full mirror of master repository --- only smal subset of branches. May be there are some common techniques for this task or some usefull h

Re: [Dri-devel] Only "normal" DRI and Mesa CVS access as developer,now?

2003-06-24 Thread Keith Whitwell
Keith Whitwell wrote: Michel Dänzer wrote: On Mon, 2003-06-23 at 20:24, José Fonseca wrote: On Mon, Jun 23, 2003 at 06:58:39PM +0200, Dieter Nützel wrote: These sourceforge "backup" server move is very annoying. It's hindering open source so much. Do we have other options? [...] If not then

Re: [Dri-devel] radeon triangle fan hang

2003-06-24 Thread Keith Whitwell
[EMAIL PROTECTED] wrote: On Tue, Jun 24, 2003 at 02:13:17PM +0100, Keith Whitwell wrote: Please try this diff - it may fix the problem in a lot of cases. I'll try it later to see if I'm missing something here, but the first thought is that NEW_BUFFER() isn't called because GET_CURRENT_VB_MAX_ELT

Re: [Dri-devel] radeon triangle fan hang

2003-06-24 Thread Keith Whitwell
[EMAIL PROTECTED] wrote: On Tue, Jun 24, 2003 at 02:13:17PM +0100, Keith Whitwell wrote: Please try this diff - it may fix the problem in a lot of cases. I'll try it later to see if I'm missing something here, but the first thought is that NEW_BUFFER() isn't called because GET_CURRENT_VB_MAX_ELT

Re: [Dri-devel] Only "normal" DRI and Mesa CVS access as developer,now?

2003-06-24 Thread Keith Whitwell
Michel Dänzer wrote: On Mon, 2003-06-23 at 20:24, José Fonseca wrote: On Mon, Jun 23, 2003 at 06:58:39PM +0200, Dieter Nützel wrote: These sourceforge "backup" server move is very annoying. It's hindering open source so much. Do we have other options? [...] If not then the solution would imp

Re: [Dri-devel] radeon triangle fan hang

2003-06-24 Thread leahcim
On Tue, Jun 24, 2003 at 02:13:17PM +0100, Keith Whitwell wrote: > Please try this diff - it may fix the problem in a lot of cases. I'll try it later to see if I'm missing something here, but the first thought is that NEW_BUFFER() isn't called because GET_CURRENT_VB_MAX_ELTS() always returns 300?

Re: [Dri-devel] Only "normal" DRI and Mesa CVS access asdeveloper, now?

2003-06-24 Thread Michel Dänzer
On Mon, 2003-06-23 at 20:24, José Fonseca wrote: > On Mon, Jun 23, 2003 at 06:58:39PM +0200, Dieter Nützel wrote: > > These sourceforge "backup" server move is very annoying. > > It's hindering open source so much. > > > > Do we have other options? [...] > If not then the solution would imply m

Re: [Dri-devel] 3rd TMU on radeon

2003-06-24 Thread Michel Dänzer
On Mon, 2003-06-23 at 18:08, Andreas Stenglein wrote: > > Am 2003.06.23 12:17:26 +0200 schrieb(en) Michel Dänzer: > > On Sat, 2003-06-21 at 14:14, Andreas Stenglein wrote: > > > > > > + init_rgba_st_st_st(); > > > + init_rgba_spec_st_st_st(); > > > + init_st_st_st_n(); > > > + init_rgpa_

Re: [Dri-devel] Only "normal" DRI and Mesa CVS access as developer, now?

2003-06-24 Thread Alex Deucher
what about https://savannah.nongnu.org/ Alex --- Martin Spott <[EMAIL PROTECTED]> wrote: > Jos? Fonseca <[EMAIL PROTECTED]> wrote: > > > If not then the solution would imply moving the CVS repository to a > new > > machine, but where would that be? XFree86.org? Some SF look-a-like? > > As far a

Re: [Dri-devel] radeon triangle fan hang

2003-06-24 Thread Keith Whitwell
Please try this diff - it may fix the problem in a lot of cases. Keith Warning: Remote host denied X11 forwarding. Index: radeon_tcl.c === RCS file: /cvsroot/dri/xc/xc/lib/GL/mesa/src/drv/radeon/radeon_tcl.c,v retrieving revision 1.8

Re: [Dri-devel] Savage-1_0_0-branch

2003-06-24 Thread Alan Hourihane
On Tue, Jun 24, 2003 at 06:00:57PM +0600, Dimitry N. Naldaev wrote: > В сообщении от 24 Июнь 2003 15:19 Alan Hourihane написал: > > I'm still looking at the large differences in the 2D driver code, so I > > thought I'd ask if someone wanted to step up and fix the 3D driver which > > will also need

RE: [Dri-devel] radeon drm in 2.5.73

2003-06-24 Thread Alexander Stohr
i am reading the list and i have not seen a fix for this. maybe the root cause is somewhere else, like using an uniprocessor config of an alternate CPU or a non current CPU desing ( -Original Message- > From: Warren Turkal [mailto:[EMAIL PROTECTED] > Sent: Tuesday, June 24, 2003 04:54 > To

Re: [Dri-devel] Configuration per application

2003-06-24 Thread Damien Miller
Felix Kühling wrote: > Hi, > > I have some questions about OS specific ways to find out the name of a > running programme outside function main. extern chat *__progname; works on OpenBSD, NetBSD and Linux. -d --- This SF.Net email is spon

Re: [Dri-devel] Savage-1_0_0-branch

2003-06-24 Thread Dimitry N. Naldaev
В сообщении от 24 Июнь 2003 15:19 Alan Hourihane написал: > I'm still looking at the large differences in the 2D driver code, so I > thought I'd ask if someone wanted to step up and fix the 3D driver which > will also need some fairly large changes to get it to compile. What need to be fixed in 3D

[Dri-devel] Configuration per application

2003-06-24 Thread Felix Kühling
Hi, I have some questions about OS specific ways to find out the name of a running programme outside function main. The following section verbosely introduces the problem and what information I found so far. You may just skip down to "Questions". I hope someone can fill in the blanks. The new con

Re: [Dri-devel] Savage-1_0_0-branch

2003-06-24 Thread Alan Cox
On Maw, 2003-06-24 at 10:19, Alan Hourihane wrote: > I'm still looking at the large differences in the 2D driver code, so I > thought I'd ask if someone wanted to step up and fix the 3D driver which > will also need some fairly large changes to get it to compile. Ditto the CLE266 via driver. So fa

[Dri-devel] Your buglist for The XFree86 Project's Bugzilla needs attention.

2003-06-24 Thread bugadmin
[This e-mail has been automatically generated.] You have one or more bugs assigned to you in the Bugzilla bugsystem (http://bugs.xfree86.org/) that require attention. All of these bugs are in the NEW state, and have not been touched in 7 days or more. You need to take a look at th

[Dri-devel] Savage-1_0_0-branch

2003-06-24 Thread Alan Hourihane
I'm still looking at the large differences in the 2D driver code, so I thought I'd ask if someone wanted to step up and fix the 3D driver which will also need some fairly large changes to get it to compile. Alan. --- This SF.Net email is sponso

Re: [Dri-devel] radeon drm in 2.5.73

2003-06-24 Thread Michel Dänzer
On Tue, 2003-06-24 at 04:53, Warren Turkal wrote: > I have a problem with the radeon drm in kernel 2.5.73. When modprobing the > module, it comes back with "radeon: Unknown symbol flush_tlb_all" and won't > load. This has been happening for at least 5 kernel versions I believe. Is > there a know

[Dri-devel] radeon drm in 2.5.73

2003-06-24 Thread Warren Turkal
I have a problem with the radeon drm in kernel 2.5.73. When modprobing the module, it comes back with "radeon: Unknown symbol flush_tlb_all" and won't load. This has been happening for at least 5 kernel versions I believe. Is there a known fix or patch that has not made it into the kernel proper