On Sat, Jan 17, 2004 at 04:55:15PM +0100, Michel D?nzer wrote: > On Sat, 2004-01-17 at 04:48, Micha Feigin wrote: > > > > There does seem to be a point to completely shutdown dri when leaving X > > and restarting on entry which would seem at list > > BTW, I think you mean 'at least' instead of 'at list'? Took me a while > to understand what you mean. :) >
Yes, sorry I keep making that mistake. The problems of english as a second language, and the speller doesn't catch that one ;-) > > on the surface to support to accelerated X servers running on the same > > machine possibly at different color depths (I had problems with a second > > one especially with a different color depth), > > http://penguinppc.org/~daenzer/DRI/radeon-reinit.diff works fine with > several servers at the same depth, but there are also problems with > different depths. > The reason I mentioned shutting DRI down completely is that it looks like its allocating a memory window on startup and releases it only on shutdown. Thus if you have two servers running they would be sharing the video memory instead of letting the active server control all the memory, which can both degrade performance and cause trouble when you have two or three high resolution true color servers running in parallel. It may also solve the problem of running two servers with different depths in parallel. I forgot to remove the allocation code at first when playing around with the changes which caused an out of memory error after the second VT switch, which seems to point in the possibility of the memory problem way. I will try to do a complete DRI shutdown/restart on VT switch later and see if it enables two servers of different depths to run in parallel (would be nice since the mach64 is so mediocre that I get proper 3D acceleration only with 16bpp but images don't look that good at that depth so that way I can ran one server for games and another for movies and the rest). > > > + int ret; > > + /* int major, minor, patch; > > + > > + DRIQueryVersion( &major, &minor, &patch ); > > + > > + if (minor >= 9) { */ > > + xf86DrvMsg( pScreen->myNum, X_INFO, > > + "[RESUME] Attempting to re-init Mach64 hardware.\n"); > > + /* } else { > > + xf86DrvMsg(pScreen->myNum, X_WARNING, > > + "[RESUME] Cannot re-init Mach64 hardware, DRM too old\n" > > + "(need 1.9.0 or newer)\n"); > > + return; > > + } */ > > You can remove the commented out code. The radeon driver checks for the > DRM minor version to make sure the resume ioctl is available. You don't > seem to need a new ioctl at all, checking for the DRI version doesn't > make sense here. Missed that one when cleaning up, thanks. I tried the ioctl, but that only made things stop working on VT switch, seems like the mach64 doesn't have whatever the radeon needs to reset. > > > -- > Earthling Michel D??nzer | Debian (powerpc), X and DRI developer > Libre software enthusiast | http://svcs.affero.net/rm.php?r=daenzer > > > > ------------------------------------------------------- > The SF.Net email is sponsored by EclipseCon 2004 > Premiere Conference on Open Tools Development and Integration > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > http://www.eclipsecon.org/osdn > -- > _______________________________________________ > Dri-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/dri-devel > ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
