On Tue, 18 Jan 2005 16:31:48 +0100, Roland Scheidegger
<[EMAIL PROTECTED]> wrote:
> Alex Deucher wrote:
> > Actually DRIAdjustframe() and friends in dri.c may still be the
> > problem.  it does some wrapping of the adjustframe() functions and
> > calls them, perhaps incorrectly for mergedfb.  I could be wrong though
> > I haven't really traced all that is going on there.  Something is
> > causing the frames to both end up at 0 when pageflipping.
> Wouldn't you get errors with non-pageflip if the wrapping is wrong for
> mergedfb? The only difference with pageflip is that the drm will
> actually use the offset values, but DRIAdjustframe and RADEONAdjustFrame
> should be called exactly the same I think (unless pageflip causes some
> other effects I can't see, like for instance pDRIPriv->fullscreen to go
> true).
> 
> Roland
> 

Yeah, you're right.  I just don't know why the new crtc offsets don't
seem to make it down to the drm.  Just thinking out loud...

Alex


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
--
_______________________________________________
Dri-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to