Re: Property plugins
Re: Property plugins
- Subject: Re: Property plugins
- From: Jeff Moore <email@hidden>
- Date: Thu, 5 Dec 2002 16:04:28 -0800
On Thursday, December 5, 2002, at 01:43 PM, Emmett James wrote:
On Thu, Dec 05, 2002 at 03:05:56PM +0100, Laurent Cerveau wrote:
Thanks, Laurent, this is extremely helpful.
At first in the Plugin open code
you need to get a reference to this control (i.e an io_connect_t that
we will call gReferenceToMyCustomControl here)
Could you illustrate how the Plugin gets this reference from the KEXT?
You need to crawl the IORegistry yourself to get the reference to the
control. The HAL will pass you the io_object_t for both your
IOAudioDevice and your IOAudioEngine. From there, you are on your own.
The routines in <IOKit/IOKitLib.h> are what you will be using.
Now in your plugin code
when you get the custom property passes to your plugin this should be
received by your handler.
I'm having a bit of trouble parsing this sentence.
What Laurent is trying to say is that in your driver, you have to
install a handler for the appropriate IORegistry changes so that when
your plug-in sets a value in the IORegistry, your driver will pick up
the change and act on it.
You are basically dealing with your driver on the IOKit user-client
level, so everything you would do there, you would have to do in your
plug-in.
--
Jeff Moore
Core Audio
Apple
_______________________________________________
coreaudio-api mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/coreaudio-api
Do not post admin requests to the list. They will be ignored.