[wdmaudiodev] Re: Destination of IOCTL

  • From: Jake Alley <jakealley26@xxxxxxxxx>
  • To: wdmaudiodev@xxxxxxxxxxxxx
  • Date: Wed, 4 Aug 2010 08:34:06 -0700 (PDT)

Bear in mind I'm talking off the top of my head.  I'm not an expert on this 
subject, but why would you want to use ioctl to send automation requests to a 
driver?  Aren't the interfaces exposed at the user level?

The other thing is wouldn't CMiniportWaveCyclic and CMiniportWaveCyclicStream 
keep their own states that you could query using global pointers for use with 

From: Robert Bielik <robert.bielik@xxxxxxxxxx>
To: wdmaudiodev@xxxxxxxxxxxxx
Sent: Wed, August 4, 2010 7:27:33 AM
Subject: [wdmaudiodev] Re: Destination of IOCTL

Jake Alley skrev:
> What are the class names of the objects you're talking about?  You can use 
>global pointers to access just about anything you want.  Synchronization is 
>another issue, something I'm not quite sure about myself.

There are the CMiniportWaveCyclic, and CMiniportWaveCyclicStream. I tried to 
setup a property request handler with a given set GUID in the Automation table 
of the miniport,
and use DeviceIoControl to send to the pin handle, but I get error 1170 ("The 
property set specified does not exist on the object.")

Sending to the filter object is no problem.


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: