Re: Property plugins
Re: Property plugins
- Subject: Re: Property plugins
- From: Jeff Moore <email@hidden>
- Date: Wed, 11 Dec 2002 11:17:29 -0800
On Wednesday, December 11, 2002, at 05:15 AM, Emmett James wrote:
On Wed, Dec 11, 2002 at 06:46:22AM -0600, Emmett James wrote:
this->setProperty(kIOAudioEngineCoreAudioPlugInKey,
kPropertyPluginName);
where kPropertyPluginName is #defined as "MyPropertyPlugin.bundle".
The path is relative to /System/Library/Extensions, so the HAL will be
looking for a bundle at
/System/Library/Extensions/MyPropertyPlugin.bundle. Is this really
where you are installing your bundle? Usually, it is installed in the
Resources directory of your kext, so the path wouldn't be what you are
setting it to.
Sadly, setting this property makes my audio devices become invisible.
The HAL doesn't see them, even though the KEXT loads and initializes
fine. If I comment out that line, the devices show up and the driver
works fine.
This is a bug in the HAL. It fails to publish devices whose plug-ins
fail for some reason.
I forgot to mention, I have some printf trace statements in my plugin's
AudioDriverPlugInOpen(), and I don't see output from them anywhere.
(BTW, do these go to /var/log/system.log, or the console?).
printf goes to the console. Syslog(3) goes to /var/log/system.log.
So it looks like my plugin is not being found by the HAL, or maybe it
is found, but maybe HAL thinks there is something wrong with it and so
won't try to call the AudioDriverPlugInOpen() function.
I think the path to your plug-in is incorrect so the HAL isn't finding
your plug-in which is triggering the bug in the HAL that is causing
your device to go unrecognized. I bet once you get the path right,
things will start working more like you expect.
--
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.