On Mit, 2002-09-18 at 16:19, Michel Dänzer wrote: > On Mit, 2002-09-18 at 15:23, Krzysztof Halasa wrote: > > Michel Dänzer <[EMAIL PROTECTED]> writes: > > > > > > IMHO we should just call RADEONAdjustFrame for cloned display as it > > > > is an internal task, not related to any other XFree86 activity. The > > > > rest of the server only knows about the primary (and secondary) screen. > > > > So this is the correct fix and not a workaround. > > > > > > But what if pScrn->AdjustFrame() is called from outside the driver? > > > > AdjustFrame for cloned screen should never be called from outside > > I think. The "outside" doesn't even know of the clone display. > > Ah, I was missing the 1 passed as a flag to RADEONAdjustFrame(), so I > didn't see the difference to pScrn->AdjustFrame() being called by driver > independent code.
I think a dedicated RADEONCloneAdjustFrame() function would be less confusing though, and wouldn't break if 1 should ever have a driver independent meaning as a flag to AdjustFrame(). -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast _______________________________________________ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
