Mailinglist Archive: radeonhd (307 mails)

[Alex Deucher <alexdeucher@xxxxxxxxx>]

On Wed, Feb 11, 2009 at 7:03 AM, Matthias Hopf <mhopf@xxxxxxx> wrote:
> On Feb 10, 09 14:24:44 -0500, Alex Deucher wrote:
> > > That's not what I had in mind. To copy an overlaping area you simply
> > > copy the entire area to off-screen video-memory. Then copy it from that
> > > off-screen memory to the final destination in the frame buffer.
>
> Yes, and I explained why this would be beneficial compared to the
> current solution.
>
> > I tried that, but got very strange behavior that I can't explain. If
> > you were to say move a window to the right, the desktop background
> > would fill in in the exposed area, but the the window contents
> > wouldn't show up in the newly covered area.  The same thing happened
> > to the temp copy.
>
> Sounds like either memory management issues, or you didn't let the
> engine wait for the destination caches to be flushed. And/or didn't
> flush the source caches, on each copy pass.

That's what I thought as well, but the caches are being flushed (they
are queued in the command stream at least).  I even tried waiting for
the engine to idle between each copy.

Alex
-- 
To unsubscribe, e-mail: radeonhd+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: radeonhd+help@xxxxxxxxxxxx