Re: [Dri-devel] new 2048 limit code...

2003-10-24 Thread Alex Deucher
Unless anyone says otherwise, I'm going to remove this code. All it has done is generate complaints from MergedFB users. Apparently it doesn't hurt anything (ie. cause a crash) to leave direct rendering enabled if the virtual desktop is larger than 2048. Since MergedFB users seem to be the only

Re: [Dri-devel] new 2048 limit code...

2003-10-18 Thread Michel Dänzer
On Sat, 2003-10-18 at 12:27, Keith Whitwell wrote: > Eric Anholt wrote: > > On Fri, 2003-10-17 at 17:27, Alex Deucher wrote: > > > >>perhaps we can not disable the DRI if mergedfb is active and the viral > >>is larger than 2048? It was only MergedFB which made this necessary... > > Maybe in the

Re: [Dri-devel] new 2048 limit code...

2003-10-18 Thread Alan Hourihane
On Fri, Oct 17, 2003 at 05:27:36PM -0700, Alex Deucher wrote: > >I've had several mergedfb users complain about the 2048 DRI limit > put in yesterday: > > else if ( pScrn->virtualX > 2048 || pScrn->virtualY > 2048 ) { > info->directRenderingEnabled = FALSE; >

Re: [Dri-devel] new 2048 limit code...

2003-10-17 Thread Eric Anholt
On Fri, 2003-10-17 at 17:27, Alex Deucher wrote: >I've had several mergedfb users complain about the 2048 DRI limit > put in yesterday: > > else if ( pScrn->virtualX > 2048 || pScrn->virtualY > 2048 ) { > info->directRenderingEnabled = FALSE; > xf86DrvMsg(sc

[Dri-devel] new 2048 limit code...

2003-10-17 Thread Alex Deucher
I've had several mergedfb users complain about the 2048 DRI limit put in yesterday: else if ( pScrn->virtualX > 2048 || pScrn->virtualY > 2048 ) { info->directRenderingEnabled = FALSE; xf86DrvMsg(scrnIndex, X_WARNING, "Dire