Re: [Dri-devel] Re: XAA versioning?

2002-10-04 Thread Michel Dänzer
On Sam, 2002-10-05 at 01:29, Chad Page wrote: > > I checked out latest CVS earlier and compiled it, it seems to work > fine now. Yes, I tracked this down together with Kevin Puetz. Glad to hear the fix works for you as well. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (power

Re: [Dri-devel] Re: XAA versioning?

2002-10-04 Thread Chad Page
I checked out latest CVS earlier and compiled it, it seems to work fine now. - Chad On 1 Oct 2002, Michel [ISO-8859-1] Dänzer wrote: > On Mon, 2002-09-30 at 02:18, Chad Page wrote: > > > > Nope, dosen't work with that - I still have to comment out the > > call in RADEONR

Re: [Dri-devel] Re: XAA versioning?

2002-10-01 Thread Chad Page
That's strange, since it only sig11's in dual head mode when only MMIO is in use... I'll look at it some more tonight. - Chad On 1 Oct 2002, Michel [ISO-8859-1] Dänzer wrote: > On Mon, 2002-09-30 at 02:18, Chad Page wrote: > > > > Nope, dosen't work with that - I still h

Re: [Dri-devel] Re: XAA versioning?

2002-10-01 Thread Michel Dänzer
On Mon, 2002-09-30 at 02:18, Chad Page wrote: > > Nope, dosen't work with that - I still have to comment out the > call in RADEONResetVideo. Appears to be a failure within the sync function > itself. Hmm, I changed RADEONWaitForIdleMMIO() to info->accel->Sync() because the former doesn't

Re: [Dri-devel] Re: XAA versioning?

2002-09-29 Thread Chad Page
Nope, dosen't work with that - I still have to comment out the call in RADEONResetVideo. Appears to be a failure within the sync function itself. - Chad On 30 Sep 2002, Michel [ISO-8859-1] Dänzer wrote: > On Son, 2002-09-29 at 19:24, Chad Page wrote: > > > > On 29 Sep 2002, M

Re: [Dri-devel] Re: XAA versioning?

2002-09-29 Thread Michel Dänzer
On Son, 2002-09-29 at 19:24, Chad Page wrote: > > On 29 Sep 2002, Michel [ISO-8859-1] Dänzer wrote: > > > On Son, 2002-09-29 at 04:47, Chad Page wrote: > > > > > > I did my own build from CVS and copied libxaa.a from it into the > > > modules directory - 2D and 3D work with one head but I s

Re: [Dri-devel] Re: XAA versioning?

2002-09-29 Thread Chad Page
On 29 Sep 2002, Michel [ISO-8859-1] Dänzer wrote: > On Son, 2002-09-29 at 04:47, Chad Page wrote: > > > > I did my own build from CVS and copied libxaa.a from it into the > > modules directory - 2D and 3D work with one head but I still get signal 11 > > with two heads, with and without xin

Re: [Dri-devel] Re: XAA versioning?

2002-09-29 Thread Chad Page
On 29 Sep 2002, Michel [ISO-8859-1] Dänzer wrote: > On Son, 2002-09-29 at 04:47, Chad Page wrote: > > > > I did my own build from CVS and copied libxaa.a from it into the > > modules directory - 2D and 3D work with one head but I still get signal 11 > > with two heads, with and without xi

Re: [Dri-devel] Re: XAA versioning?

2002-09-29 Thread Michel Dänzer
On Son, 2002-09-29 at 04:47, Chad Page wrote: > > I did my own build from CVS and copied libxaa.a from it into the > modules directory - 2D and 3D work with one head but I still get signal 11 > with two heads, with and without xinerama. I can disable acceleration and > it will work, so th

Re: [Dri-devel] Re: XAA versioning?

2002-09-28 Thread Chad Page
I did my own build from CVS and copied libxaa.a from it into the modules directory - 2D and 3D work with one head but I still get signal 11 with two heads, with and without xinerama. I can disable acceleration and it will work, so there seems to be another xaa problem with shared entitie

Re: [Dri-devel] Re: XAA versioning?

2002-09-24 Thread Michel Dänzer
On Die, 2002-09-24 at 17:55, Stephane Chauveau wrote: > On Sun, Sep 22, 2002 at 10:33:15PM +0200, Michel Dänzer wrote: > > Several people on IRC reported crashes in the 2D code with the current > > trunk snapshots. I realized they are due to the TwoPoint acceleration > > functions depending on

[Dri-devel] Re: XAA versioning?

2002-09-24 Thread Stephane Chauveau
On Sun, Sep 22, 2002 at 10:33:15PM +0200, Michel Dänzer wrote: > Several people on IRC reported crashes in the 2D code with the current > trunk snapshots. I realized they are due to the TwoPoint acceleration > functions depending on XAA changes. How can we handle this, bump the XAA > version