Re: Correct Video Port Architecture
- From: "Damon Barry [MSFT]" <damonb@xxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 10 May 2005 12:34:46 -0700
I think you have the right idea; since you don't know what will be connected
to the video port, your display driver is not responsible for initializing
it. The drivers for the TV decoder, camera, etc should be responsible for
initializing those devices.
I've used video ports before for displaying decoded DVD program streams onto
the device display, using a DDraw overlay. The DVD decoder/renderer HW had
a driver that fit into the CE driver model, and was initialized at boot
time. A registry key or interface was used to switch the data flow from
TV/audio out jacks to the video port output. The display driver also fit
into the CE driver model. My DVD player app initialized the primary
surface, set up the color key, created a video port object and an overlay
surface, associated the two, and called StartVideo to allow data flow over
the video port onto the overlay. I believe an app on your hardware would do
something similar.
--
damonb@xxxxxxxxxxxxxxxxxxxx (Remove the 'online.' from my address to reach
me.)
This posting is provided "AS IS" with no warranties, and confers no rights.
______________________________
The Windows CE 5.0 documentation is online at:
http://msdn.microsoft.com/library/en-us/wceintro5/html/wce50oriWelcomeToWindowsCE.asp?frame=true
"Rui Tang" <tangrui76_nospam@xxxxxxxxxxx> wrote in message
news:%23y3IDicUFHA.3176@xxxxxxxxxxxxxxxxxxxxxxx
> I am not sure about how to partition the code for the VideoPort support
> in our chip's display driver.
>
> The videoport capability is supposed to be exposed by the directdraw
> display driver. That is to say, it is should be chip specific and part of
> the CSP, since our SOC chip owns the hardware interface for lcd and video
> input port. However, what will be finally connected to the video input
> port to our chip is platform specific. As different platform may have
> different parts connected to the hardware video input port. For example,
> it may be a TV decoder or a camera sensor.
>
> Where should be the code for init the TV decoder/camera sensor be placed
> then?
>
> When an application calls CreateVideoPort and StartVideo, the TV
> decoder/camera are supposed to be inited and started then, but where the
> code doing that should be placed? If embedded in the directdraw driver,
> then it means that every time when portint to a new platform, the display
> driver need to be changed. This is something I highly dislike as I want to
> abstract the display driver purely from the platform implementation.
>
> Maybe I am not understanding the VideoPort concept very correctly? Or do
> I miss something? Any comments are welcome.
>
>
> Rui
>
>
>
>
>
>
.
- Follow-Ups:
- Re: Correct Video Port Architecture
- From: Rui Tang
- Re: Correct Video Port Architecture
- References:
- Correct Video Port Architecture
- From: Rui Tang
- Correct Video Port Architecture
- Prev by Date: Re: The direct show meets exception
- Next by Date: Platform builder change the display name
- Previous by thread: Correct Video Port Architecture
- Next by thread: Re: Correct Video Port Architecture
- Index(es):
Relevant Pages
|
|
