Re: [Dri-devel] TCL Testing...

2002-02-22 Thread Keith Whitwell

Adam K Kirchhoff wrote:
> 
> On Fri, 22 Feb 2002, Ian Romanick wrote:
> 
> > On Fri, Feb 22, 2002 at 01:32:23PM -0500, Adam K Kirchhoff wrote:
> > >
> > > On Fri, 22 Feb 2002, Keith Whitwell wrote:
> > >
> > > > Adam K Kirchhoff wrote:
> > > > >
> > > > > So, even though I'm pretty sure the Mobility chips don't even have
> > > > > the TCL functionality to begin with, I thought I'd test the new Radeon
> > > > > code on my Compaq Presario 2700 (Mobility LY chip) just to see if it broke
> > > > > anything :-)
> > > > >
> > > > > Well, it did...  When I start up a 3D application, the window gets
> > > > > placed on the desktop, and then X all but locks up.  The mouse still
> > > > > works, but the entire X server is unresponsive..  It's impossible to move
> > > > > or kill any window, or even kill the X server.
> > > >
> > > > I need to add checks for the Mobility chips & disable tcl in those cases.  I
> > > > can do this pretty quickly...  You can test yourself what I'm going to do just
> > > > by setting "RADEON_NO_TCL=t" before running anything.
> > > >
> > > > Let me know if this works...
> > >
> > > No luck.
> > >
> > > $ export RADEON_NO_TCL=t
> > > $ glxgears
> >
> > I suspect this may have been a typo in the original message.  It probably
> > sould be "RADEON_NO_TCL=y".  'y' and 't' are neighbors, afterall. :)

It really just checks for the existence of the 'RADEON_NO_TCL' env var.  

Keith

___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel



Re: [Dri-devel] TCL Testing... (fwd)

2002-02-22 Thread Keith Whitwell

Adam K Kirchhoff wrote:
> 
> Just a quick follow-up to a question I'm sure that's coming :-)
> 
> Yes, the Radeon mobility works fine under stock 4.2.0, without any
> problems.
> 

Jens also pointed out that I'd neglected to update the test for kernel module
versions - is it possible that you've been running with an older version?  

Actually before you answer, I've got to commit a fix for broken compatibility
on the tcl- branch, which could well be screwing you over.

Keith

___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel



Re: [Dri-devel] TCL Testing...

2002-02-22 Thread Keith Whitwell

Adam K Kirchhoff wrote:
> 
> On Fri, 22 Feb 2002, Keith Whitwell wrote:
> 
> > Adam K Kirchhoff wrote:
> > >
> > > So, even though I'm pretty sure the Mobility chips don't even have
> > > the TCL functionality to begin with, I thought I'd test the new Radeon
> > > code on my Compaq Presario 2700 (Mobility LY chip) just to see if it broke
> > > anything :-)
> > >
> > > Well, it did...  When I start up a 3D application, the window gets
> > > placed on the desktop, and then X all but locks up.  The mouse still
> > > works, but the entire X server is unresponsive..  It's impossible to move
> > > or kill any window, or even kill the X server.
> >
> > I need to add checks for the Mobility chips & disable tcl in those cases.  I
> > can do this pretty quickly...  You can test yourself what I'm going to do just
> > by setting "RADEON_NO_TCL=t" before running anything.
> >
> > Let me know if this works...
> 
> No luck.
> 
> $ export RADEON_NO_TCL=t
> $ glxgears
> 
> Still causes the lockup.  I can pass along my XFree86.0.log logfile is
> you'd like, though I don't see anything particularly telling in it.

OK, it looks like it's not enough to never issue tcl triangles - I'll do a
more thorough job of disabling things.

Keith

___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel



Re: [Dri-devel] TCL Testing...

2002-02-22 Thread Adam K Kirchhoff


On Fri, 22 Feb 2002, Ian Romanick wrote:

> On Fri, Feb 22, 2002 at 01:32:23PM -0500, Adam K Kirchhoff wrote:
> > 
> > On Fri, 22 Feb 2002, Keith Whitwell wrote:
> > 
> > > Adam K Kirchhoff wrote:
> > > > 
> > > > So, even though I'm pretty sure the Mobility chips don't even have
> > > > the TCL functionality to begin with, I thought I'd test the new Radeon
> > > > code on my Compaq Presario 2700 (Mobility LY chip) just to see if it broke
> > > > anything :-)
> > > > 
> > > > Well, it did...  When I start up a 3D application, the window gets
> > > > placed on the desktop, and then X all but locks up.  The mouse still
> > > > works, but the entire X server is unresponsive..  It's impossible to move
> > > > or kill any window, or even kill the X server.
> > > 
> > > I need to add checks for the Mobility chips & disable tcl in those cases.  I
> > > can do this pretty quickly...  You can test yourself what I'm going to do just
> > > by setting "RADEON_NO_TCL=t" before running anything.
> > > 
> > > Let me know if this works...
> > 
> > No luck.  
> > 
> > $ export RADEON_NO_TCL=t
> > $ glxgears
> 
> I suspect this may have been a typo in the original message.  It probably
> sould be "RADEON_NO_TCL=y".  'y' and 't' are neighbors, afterall. :)

Still no luck :-)

Adam



___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel



Re: [Dri-devel] TCL Testing...

2002-02-22 Thread Ian Romanick

On Fri, Feb 22, 2002 at 01:32:23PM -0500, Adam K Kirchhoff wrote:
> 
> On Fri, 22 Feb 2002, Keith Whitwell wrote:
> 
> > Adam K Kirchhoff wrote:
> > > 
> > > So, even though I'm pretty sure the Mobility chips don't even have
> > > the TCL functionality to begin with, I thought I'd test the new Radeon
> > > code on my Compaq Presario 2700 (Mobility LY chip) just to see if it broke
> > > anything :-)
> > > 
> > > Well, it did...  When I start up a 3D application, the window gets
> > > placed on the desktop, and then X all but locks up.  The mouse still
> > > works, but the entire X server is unresponsive..  It's impossible to move
> > > or kill any window, or even kill the X server.
> > 
> > I need to add checks for the Mobility chips & disable tcl in those cases.  I
> > can do this pretty quickly...  You can test yourself what I'm going to do just
> > by setting "RADEON_NO_TCL=t" before running anything.
> > 
> > Let me know if this works...
> 
> No luck.  
> 
> $ export RADEON_NO_TCL=t
> $ glxgears

I suspect this may have been a typo in the original message.  It probably
sould be "RADEON_NO_TCL=y".  'y' and 't' are neighbors, afterall. :)

-- 
Tell that to the Marines!

___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel



Re: [Dri-devel] TCL Testing... (fwd)

2002-02-22 Thread Adam K Kirchhoff


Just a quick follow-up to a question I'm sure that's coming :-)

Yes, the Radeon mobility works fine under stock 4.2.0, without any
problems.

-- Forwarded message --
Date: Fri, 22 Feb 2002 13:32:23 -0500 (EST)
From: Adam K Kirchhoff <[EMAIL PROTECTED]>
To: Keith Whitwell <[EMAIL PROTECTED]>
Cc: dri-devel <[EMAIL PROTECTED]>
Subject: Re: [Dri-devel] TCL Testing...


On Fri, 22 Feb 2002, Keith Whitwell wrote:

> Adam K Kirchhoff wrote:
> > 
> > So, even though I'm pretty sure the Mobility chips don't even have
> > the TCL functionality to begin with, I thought I'd test the new Radeon
> > code on my Compaq Presario 2700 (Mobility LY chip) just to see if it broke
> > anything :-)
> > 
> > Well, it did...  When I start up a 3D application, the window gets
> > placed on the desktop, and then X all but locks up.  The mouse still
> > works, but the entire X server is unresponsive..  It's impossible to move
> > or kill any window, or even kill the X server.
> 
> I need to add checks for the Mobility chips & disable tcl in those cases.  I
> can do this pretty quickly...  You can test yourself what I'm going to do just
> by setting "RADEON_NO_TCL=t" before running anything.
> 
> Let me know if this works...

No luck.  

$ export RADEON_NO_TCL=t
$ glxgears

Still causes the lockup.  I can pass along my XFree86.0.log logfile is
you'd like, though I don't see anything particularly telling in it.

Adam




___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel



Re: [Dri-devel] TCL Testing...

2002-02-22 Thread Adam K Kirchhoff


On Fri, 22 Feb 2002, Keith Whitwell wrote:

> Adam K Kirchhoff wrote:
> > 
> > So, even though I'm pretty sure the Mobility chips don't even have
> > the TCL functionality to begin with, I thought I'd test the new Radeon
> > code on my Compaq Presario 2700 (Mobility LY chip) just to see if it broke
> > anything :-)
> > 
> > Well, it did...  When I start up a 3D application, the window gets
> > placed on the desktop, and then X all but locks up.  The mouse still
> > works, but the entire X server is unresponsive..  It's impossible to move
> > or kill any window, or even kill the X server.
> 
> I need to add checks for the Mobility chips & disable tcl in those cases.  I
> can do this pretty quickly...  You can test yourself what I'm going to do just
> by setting "RADEON_NO_TCL=t" before running anything.
> 
> Let me know if this works...

No luck.  

$ export RADEON_NO_TCL=t
$ glxgears

Still causes the lockup.  I can pass along my XFree86.0.log logfile is
you'd like, though I don't see anything particularly telling in it.

Adam



___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel



Re: [Dri-devel] TCL Testing...

2002-02-22 Thread Keith Whitwell

Adam K Kirchhoff wrote:
> 
> So, even though I'm pretty sure the Mobility chips don't even have
> the TCL functionality to begin with, I thought I'd test the new Radeon
> code on my Compaq Presario 2700 (Mobility LY chip) just to see if it broke
> anything :-)
> 
> Well, it did...  When I start up a 3D application, the window gets
> placed on the desktop, and then X all but locks up.  The mouse still
> works, but the entire X server is unresponsive..  It's impossible to move
> or kill any window, or even kill the X server.

I need to add checks for the Mobility chips & disable tcl in those cases.  I
can do this pretty quickly...  You can test yourself what I'm going to do just
by setting "RADEON_NO_TCL=t" before running anything.

Let me know if this works...

Keith

___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel