>> Ur explanation is very clear. YES, the StopVideo in Xv library can be called by
>> Xserver without AP's request.
>> I have a DVD player AP which will use PutImage function in Xv library to
>> display the video. When I use our own graphic card & driver, in fact, Xserver
>> will call StopVideo in my driver not only when I destroy the window but also
>> moving or cliping the window. If I remove the flag VIDEO_OVERLAID_IMAGES in my
>> driver, Xserver will never call StopVideo even though I destroy the window.
>
> Those both are the expected behavior.
>
>>
>> In ATI's driver, it also set VIDEO_OVERLAID_IMAGES flag. But I move or clip the
>> video window, Xserver never call StopVideo in ATI's driver. It is only called
>> when the window is destroy.
>
> I don't understand that. That shouldn't be the case, at least not
> of the driver that's in the XFree86 tree.
>
>> My purpose is to eliminate the flicker state when moving the video window. Coz
>> in StopVideo function, we turn off video H/W engine; in PutImage function, we
>> turn on video H/W engine, the same does ATI.
>
> Not in the driver I'm looking at. The R128 driver sets a timer and
> turns it off later.
>
> Mark.
Hi Mark & Vladimir,
I feel so sorry for that I don't mention about the version of ATI AiW r128 driver.
I got it from my colleague, and I will send it to your mailbox for ur reference.
Mark, Thanks a lot !!
You are right! I try the AiW r128 driver in XFree86 tree 4.1.0 & 4.2.0 & find that
they have the expected behavior. This means that they will call StopVideo whenever
we move the video window.
Only the special version of the AiW r128 driver has the strange behavior. Maybe the
reason is the "ReputImage" function Vladimir mentioned about. I will try it !
Kevin.
-----------------------------------------------------------------
< �C�ѳ� Yahoo!�_�� > www.yahoo.com.tw
_______________________________________________
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert
