I've overcome this, but sursprisingly there is no further segfault. I see all the debuging statements scrolling in my terminal without stoping.
This either means that the problem is at the locking mechanism or in the register programming in _tris.c. I'm really suspicious about the locking because when I first disabled the MMIO (since the driver doesn't really do PIO) and forgot about disabling the locking the my computer also hanged. How can this be? Since when the locking is overriden the computer doesn't hang this means that the problem must when locking. Any ideas? Later on I'm going to see if I can get another laptop from a friend of mine to make further debugging. Jos� Fonseca On 2002.03.01 17:35 Jos� Fonseca wrote: > Have no idea. I'm still having troubles disabling the lock, because some > of the state variables are set up when the card is locked (cliprects > e.g.), so I'm getting segfaults due to this, and not the the _real_ > problem yet. > > As soon as I overcome this and stumble into concrete problems I'll come > back to you. > > Jose Fonseca > > On 2002.03.01 17:23 Leif Delgass wrote: >> OK, where was the lockup happening after you fixed the viewport problem? >> >> On Fri, 1 Mar 2002, Jos� Fonseca wrote: >> >> > I've disabled PIO and locking and I'm now running glxgears with gdb to >> > catch all the segfaults. >> > >> > I commited so that we both can do the same thing. The patch is >> attached >> in >> > case you need to reverse it. >> > >> > Regards, >> > >> > Jos� Fonseca >> > >> >> -- >> Leif Delgass >> http://www.retinalburn.net >> _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
