Thread-topic: Kext Load on demand and daemon communication
User-agent: Microsoft-Entourage/11.3.6.070618
Hi
I am looking to understand how load-on-demand drivers interact with daemons.
I'm not an experienced driver writer, so I apologize in advance for missing
the obvious. (-:
I have a driver that sends messages to a daemon that is always running. The
daemon has other purposes besides responding to messages from this kext.
In order to listen to messages from the kext, the daemon creates a
notification port, connects to the kext, and waits for available data.
Since the daemon must connect to the kext to listen for messages from it,
the kext must be loaded, so it seems there is no load on demand benefit, it
just stays loaded.
This seems like a Catch-22 to me. I don't want the kext to load unless the
OS determines that it is needed, but if it is loaded, I need my daemon to
listen to it. I can't listen to it without loading it. Can I listen for
its loading, then listen for messages?
What's the secret to making this work?
Thanks,
Eric
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/darwin-kernel/email@hidden
This email sent to email@hidden
