A-O-A,
Finally I have given support for video overlay in my display driver and now
WinDVD is running on it. But WinDVD runs only when my display device is
primary. I am not able to get the pointer of the overlay when my display
device is secondary or when it is in mirror mode. Now What I am planning to
do is, When my display device is secondary and some other device is primary,
I want to get the pointer of the overlay memory used by the primary display
device. Can any one tell me how to do it. Is there any API by that I could
get the overlay memory pointer. Or some other way from my display driver.
THanks in advance.
Regards,
Asif
That seems odd. Are you sure that there isn’t some bug in regards to
reporting overlay functionality when your device is secondary?
You can’t just “ask the other device for it’s overlay pointer”, as that
could well be implemented in a completely different way to yours (for
instance, our chip has complete support for overlay in hardware, so our
overlay handling would be quite different than yours). [In fact, if we
don’t display an overlay in the current mode, the overlay channel is turned
off and there is no frame buffer memory (or any other memory) allocated for
the overlay channel, so what our driver would most likely return, should
you ask for such a thing, would be “Not present” or NULL or something along
those lines].
Presumably you have tried WinDVD with some other hardware on the secondary
device to see that this works, just in case it’s WinDVD being braindead
with regards to their implementation and always wants to run on the first
head?
–
Mats
xxxxx@lists.osr.com wrote on 02/16/2005 01:46:52 PM:
A-O-A,
Finally I have given support for video overlay in my display driver and
now
WinDVD is running on it. But WinDVD runs only when my display device is
primary. I am not able to get the pointer of the overlay when my display
device is secondary or when it is in mirror mode. Now What I am planning
to
do is, When my display device is secondary and some other device is
primary,
I want to get the pointer of the overlay memory used by the primary
display
device. Can any one tell me how to do it. Is there any API by that I
could
get the overlay memory pointer. Or some other way from my display driver.
THanks in advance.
Regards,
Asif
Questions? First check the Kernel Driver FAQ at http://www.
osronline.com/article.cfm?id=256
You are currently subscribed to ntdev as: xxxxx@3dlabs.com
To unsubscribe send a blank email to xxxxx@lists.osr.com
ForwardSourceID:NT0000D1CA
Ok , let I put the question in another way. Let us take the case when My
device is Primary and WinDVD is running on it. When WinDVD window is on my
device display area, overlay is used and Video is shown properly. When I
drag this WinDVD window to the secondary device display area, randering
still continues on my device overlay memory i.e. DdFlip continued to be
called with valid pointers. Although nothing is shown on the secondary
device and as we know it should not be, but if I display my device’s overlay
surface\memory at this time, it contains valid video. Is there any way we
can restrict WinDVD or any other application to not rander on the overlay
memory when its window is not on the primary device.
I don’t know about the above question so far. Now, if it is the same case
with all the other devices i.e.WinDVD continues to rander on the primary
device overlay memory regardless of where currently the winDVD window is,
Then I think we can take the pointer of overlay memory of the primary
device.
Actually I have no idea how WinDVD randers on the overlay memory. I know it
is the streaming driver that actually does randering on the overlay memory,
but whether WinDVD or any other player have or can get the pointer of the
Overlay memory is not sure. If in case WinDVD can have it, then we can also.
Regards,
Asif
Subject: Re: Getting Video Overlay memory pointer
From: Mats PETERSSON
>Date: Wed, 16 Feb 2005 13:58:46 +0000
>X-Message-Number: 9
>
>
>
>
>
>
>That seems odd. Are you sure that there isn’t some bug in regards to
>reporting overlay functionality when your device is secondary?
>
>You can’t just “ask the other device for it’s overlay pointer”, as that
>could well be implemented in a completely different way to yours (for
>instance, our chip has complete support for overlay in hardware, so our
>overlay handling would be quite different than yours). [In fact, if we
>don’t display an overlay in the current mode, the overlay channel is turned
>off and there is no frame buffer memory (or any other memory) allocated for
>the overlay channel, so what our driver would most likely return, should
>you ask for such a thing, would be “Not present” or NULL or something along
>those lines].
>
>Presumably you have tried WinDVD with some other hardware on the secondary
>device to see that this works, just in case it’s WinDVD being braindead
>with regards to their implementation and always wants to run on the first
>head?
>
>–
>Mats