> I have posted message to [Dri-devel] and they asked me to provide more
> info about xawtv (attached message). What I came upon is that xawtv
> renders images directly into framebuffer, at address obtained form
> 'v4l-conf'. Am I right.
Well, not xawtv, but the grabber card (by PCI-PCI xfer). U
> the indirect buffers aren't flushed often enough. When I move a window
> with amiwm, the contents don't move at first. Only when I move it
> again do the contents appear in the current place. A quick comparison
> with the Radeon code didn't reveal any obvious difference, so I wonder
> what's wro
> One thing that would probably be good for r128 and radeon is add the option
> back to disable CCE or CP and use the fuller 2D acceleration routines. And
> also, if DRI isn't possible for some reason then fallback to the fuller
> acceleration routines.
It already works this way: You have either
> > to the Rage128's CCE engine. Although it only accelerates SolidFill and
> > ScreenToScreenCopies it should help a lot.
>
> Hmm, maybe it's easy for someone who doesn't touch the dri code for the
> first time, but not for me. I've tried, the code builds and doesn't
> crash, but doesn't work.
> The Radeon driver has some CP code for 2D that should be easily ported
> to the Rage128's CCE engine. Although it only accelerates SolidFill and
> ScreenToScreenCopies it should help a lot.
Hmm, maybe it's easy for someone who doesn't touch the dri code for the
first time, but not for me. I've
Hi,
I've figured why the Rage 128 crashes if the bttv overlay is active (see
http://sourceforge.net/tracker/index.php?func=detail&aid=210239&group_id=387&atid=100387).
Because the r128 driver does 2D acceleration using MMIO commands, it has
to shutdown the CCE every time it wants to submit a
