Re: [Dri-devel] Re: [Dri-users] ATI RADEON 7500 DRI Drivers won'twork! V2

2002-06-29 Thread Michel Dänzer
On Sun, 2002-06-30 at 00:56, Mike Mestnik wrote: > > > > > > > > > >CONFIG_RWSEM_GENERIC_SPINLOCK is not set. > > > > >This causes thoes unresolved symbols, YOU CANT HAVE THOES :) > > > > > > > > > >There seams to be only one reason why CONFIG_RWSEM_GENERIC_SPINLOCK > > >dose > > > > >not > > >

[Dri-devel] Re: [Dri-users] ATI RADEON 7500 DRI Drivers won't work! V2

2002-06-29 Thread Mike Mestnik
> >0280 T rwsem_wake > > U schedule > > U wake_up_process > > > ># cat /proc/ksyms | grep rwsem > >c01d3730 rwsem_down_read_failed > >c01d3870 rwsem_down_write_failed > >c01d39b0 rwsem_wake > > > >--- Digital Net Assassi

[Dri-devel] Re: [Dri-users] ATI RADEON 7500 DRI Drivers won't work! V2

2002-06-29 Thread Digital Net Assassin
Hello again, I edited the ~/linux/.config file again, and did as you said: # # Processor type and features # CONFIG_M386=y CONFIG_RWSEM_GENERIC_SPINLOCK=y # CONFIG_RWSEM_XCHGADD_ALGORITHM is not set and I recompiled the kernel again, after trying to install the radeon-20020629-linux.i386

Re: [Dri-devel] Re: S3 VIRGE DRI in CVS now

2002-06-29 Thread Anders Haugen
- Original Message - From: "John J. Tobin" <[EMAIL PROTECTED]> Date: 26 Jun 2002 20:38:18 -0500 To: Massimiliano Lingua <[EMAIL PROTECTED]> Subject: [Dri-devel] Re: S3 VIRGE DRI in CVS now > On Wed, 2002-06-26 at 17:43, Massimiliano Lingua wrote: > > On Thu, 2002-06-27 at 00:24, John J.

Re: [Dri-devel] R200 kernel interfaces

2002-06-29 Thread José Fonseca
On Mon, Jun 24, 2002 at 10:08:42AM -0700, Ian Romanick wrote: >On Tue, Jun 18, 2002 at 12:09:02AM +0100, José Fonseca wrote: >> On 2002.06.17 23:19 Keith Whitwell wrote: >> > >> >> >> >> We could overcome the GLX difficulties in the same way we do now in >> >> libGL with the direct rendering. >

Re: [Dri-devel] How to trace switching to software rendering

2002-06-29 Thread Brian Paul
Michael Schlueter wrote: > Am Don, 2002-06-27 um 00.43 schrieb Brian Paul: > Most of the DRI drivers have a per-context field called 'Fallback'. It's a bitmask which records various reasons why we need to fallback to software rendering. In the case of the mga (G400) driver you'll >>

[Dri-devel] Re: [Dri-users] ATI RADEON 7500 DRI Drivers won't work! V2

2002-06-29 Thread Mike Mestnik
I did some digging. CONFIG_RWSEM_GENERIC_SPINLOCK is not set. This causes thoes unresolved symbols, YOU CANT HAVE THOES :) There seams to be only one reason why CONFIG_RWSEM_GENERIC_SPINLOCK dose not get set. CONFIG_M386 must be set to "y", then CONFIG_RWSEM_GENERIC_SPINLOCK is set to "y" else i

[Dri-devel] Increase Your Business

2002-06-29 Thread Sales Manager
Title: You are receiving this email because you registered to receive special offers from one of our marketing partners The power of Email Marketing Email Marketing is spreading around the whole world because of its high effectiveness,  spe

Re: [Dri-devel] Radeon 7500 lockup FIXED

2002-06-29 Thread Tim Smith
On Saturday 29 Jun 2002 4:05 pm, Tim Smith scribed numinously:" > In a totally unrelated note, the texture funnies that I reported earlier > do not occur in 24-bit mode, but only in 16-bit mode. Tux Racer shows > this too though in tux racer the problem is still visible in 16bit mode > though less

[Dri-devel] Radeon 7500 lockup FIXED

2002-06-29 Thread Tim Smith
I found a few other ways of provoking the problem while I was at it, and dragging an xclock window over the 3D view did it too (with a window manager and "solidmove" turned on). In fact, I also managed to provoke the lockup by persistently dragging xclock around over a maximised glxgears in 16

Re: [Dri-devel] How to trace switching to software rendering

2002-06-29 Thread Michael Schlueter
Am Don, 2002-06-27 um 00.43 schrieb Brian Paul: > >>Most of the DRI drivers have a per-context field called 'Fallback'. > >>It's a bitmask which records various reasons why we need to fallback > >>to software rendering. In the case of the mga (G400) driver you'll > >>see these flags in mgacontex