WDM to WinCE porting

Hi All,

I have to port a WDM video capture driver to WinCE ...As you
know WDM has got a stream class driver which will communicate to the
undrlying miniport driver like tuner,decoder and crossbar...the problem i am
facing is that WinCE doesnt have a video stream class driver and
architectuers are also completely different ..here no irp's ,no dpc's ,even
most of the API's used in WinCE is obsolete in WDM ...Is it advisable to try
to make my own device specific IOCTL's,since i cannot go for the WDM
specified IOCTL's ....or should i contact the chip manufacturer to get those
IOCTL's...does anyone have any previous experience of porting WDM to
WinCE....... i am at complete loss ......Any sort of useful suggestions
higly appreciated ...dont tell me to ask in Platbuilder group ..i have tried
several times but not much i got from there..

Best Regards
Soorya

Tim
Sat Mar 19 22:32:03 CST 2005

"soorya" <will_stop_ur_heartbeats@yahoo.com> wrote:
>
> I have to port a WDM video capture driver to WinCE ...As you
>know WDM has got a stream class driver which will communicate to the
>undrlying miniport driver like tuner,decoder and crossbar...the problem i am
>facing is that WinCE doesnt have a video stream class driver and
>architectuers are also completely different ..here no irp's ,no dpc's ,even
>most of the API's used in WinCE is obsolete in WDM ...Is it advisable to try
>to make my own device specific IOCTL's,since i cannot go for the WDM
>specified IOCTL's ....or should i contact the chip manufacturer to get those
>IOCTL's...

Yes, one of the fun AND frustrating things about Windows CE is that the
driver model is rather unspecific. You can basically do what you want,
since interoperability is not a big concern.

The FIRST thing you should do is check with the chip manufacturer to see if
they have Windows CE support already. No sense reinventing the wheel if
you don't have to.

The one thing you DO have in the CE world is the familiarity of DirectShow.
When I've been faced with a task like you described, I just tried to think
of the driver as a DirectShow filter, or an extension of a DirectShow
filter. Create a private API that fills in the holes in the DShow filter.

(Actually, in our case, the client had decided to run apps in kernel mode,
so the filter just did the I/O directly. Made things easier for me.)
--
- Tim Roberts, timr@probo.com
Providenza & Boekelheide, Inc

soorya
Sun Mar 20 04:12:14 CST 2005

thanx Tim for showing me a way ...will do, as u advised


warm regards
soorya

"Tim Roberts" <timr@probo.com> wrote in message
news:erup319c2j466gn04rf9q0ak1tfpldo1j3@4ax.com...
> "soorya" <will_stop_ur_heartbeats@yahoo.com> wrote:
> >
> > I have to port a WDM video capture driver to WinCE ...As you
> >know WDM has got a stream class driver which will communicate to the
> >undrlying miniport driver like tuner,decoder and crossbar...the problem i
am
> >facing is that WinCE doesnt have a video stream class driver and
> >architectuers are also completely different ..here no irp's ,no dpc's
,even
> >most of the API's used in WinCE is obsolete in WDM ...Is it advisable to
try
> >to make my own device specific IOCTL's,since i cannot go for the WDM
> >specified IOCTL's ....or should i contact the chip manufacturer to get
those
> >IOCTL's...
>
> Yes, one of the fun AND frustrating things about Windows CE is that the
> driver model is rather unspecific. You can basically do what you want,
> since interoperability is not a big concern.
>
> The FIRST thing you should do is check with the chip manufacturer to see
if
> they have Windows CE support already. No sense reinventing the wheel if
> you don't have to.
>
> The one thing you DO have in the CE world is the familiarity of
DirectShow.
> When I've been faced with a task like you described, I just tried to think
> of the driver as a DirectShow filter, or an extension of a DirectShow
> filter. Create a private API that fills in the holes in the DShow filter.
>
> (Actually, in our case, the client had decided to run apps in kernel mode,
> so the filter just did the I/O directly. Made things easier for me.)
> --
> - Tim Roberts, timr@probo.com
> Providenza & Boekelheide, Inc