[wdmaudiodev] Re: Using user defined IOCTL calls in MSVAD

  • From: AsHwAtH <itsmeash@xxxxxxxxx>
  • To: wdmaudiodev@xxxxxxxxxxxxx
  • Date: Wed, 21 Mar 2007 16:26:29 +0530

Thanks for the help!

I want to know how do i define the new IOCTL's in the MSVAD driver,
using CTL_CODE? I tried this but the <type> has to match that of KS

After adding the new IOCTL's i should be able to still use Winamp and other
applications but only my application should have additional IOCTL support.

Say, after defining this IOCTL, how do i call? DeviceIoControl needs a
handle for the device and where do i get that.

Please guide.
Thanks a lot

On 3/19/07, Tim Roberts <timr@xxxxxxxxx> wrote:

AsHwAtH wrote:
> I am currently using MSVAD driver for my application.
> Is it possible to define user defined IOTCL calls with the current
> MSVAD sample available.
> This is what I want to do.
> The 2 basic API's CopyTo and CopyFrom has to be called from my
> application through the IOTCL that i have defined instead of the
> exisiting KStreaming. (like.. KS_START, KS_RUN).
> Can this be done?
> Will defining DeviceIOControl at the start of AddDevice work? Or  is
> there a better way to do?

The documentation for PcInitializeAdapterDriver talks about this.  You
can override the DeviceControl pointer that port class sets up with your
own pointer, as long as you call PcDispatchIrp from within your own
handler to allow the standard KS IOCTLs to be handled.  I suspect you
would want to do this in your DriverEntry routine.

Tim Roberts, timr@xxxxxxxxx
Providenza & Boekelheide, Inc.


WDMAUDIODEV addresses:
Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx
Subscribe:    mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe
Unsubscribe:  mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe
Moderator:    mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx


Other related posts: