On Mon, Dec 03, 2001 at 01:18:29PM +0100, Michel D�nzer wrote: > > (I am a co-author of the DMA-enabled Xv*PutImage for r128 you mentioned) > > As you probably have detailed reports on how this DMA-enhanced Xv*PutImage > > works on nvidia, don't you have stability problems with certain players? I > > noticed that while I never had troubles with aviplay or mplayer, vlc was not > > properly programmed and one thread liked it a lot to kill a Xv*PutImage > > running in another thread (has likely been fixed already but I haven't checked > > yet), which caused total machine lockup. Xine also causes lockup from time to > > time. > If you're running 4.1, this is probably because the chip can hang when a > bus mastering operation is active while it's being reset in the course > of switching the CCE on or off. AHA! So I suppose then THIS is also the reason why km (experimental ATI capturing v4l module) doesn't mix with DRI on r128 (i.e. it causes lockup when X tries to do 2D-accelerated function). I read that CCE and DRI didn't mix well yet, but only now thnx to your email I realized this is the cause of the lockups I've been experiencing.
> This isn't an issue anymore with current CVS as it uses the CCE exclusively
> when DRI is enabled. That's why I only committed it to the DRI CVS once that
> change was made there.
Thnx dude, one point less left on my linux wishlist. Now I can throw my VCR
away :-)
Bye,
Peter Surda (Shurdeek) <[EMAIL PROTECTED]>, ICQ 10236103, +436505122023
--
...and that is how we know the Earth to be banana-shaped.
msg01995/pgp00000.pgp
Description: PGP signature
