Re: Kext Load on demand and daemon communication
Re: Kext Load on demand and daemon communication
- Subject: Re: Kext Load on demand and daemon communication
- From: Michael Smith <email@hidden>
- Date: Thu, 18 Oct 2007 18:57:53 -0700
On Oct 18, 2007, at 8:44 AM, Eric Long wrote:
I looked at IOServiceAddMatchingNotification(). That seems pretty
straight-forward. What I'm not clear on is what stage my driver
will be in
when I get a notice in my callback.
The notification will be posted as a consequence of your driver
calling registerService().
Right.
But does that mean my daemon will receive that notice before the
driver
exits registerToService()?
Assuming you mean "registerService()", then yes, that's possible.
If my daemon connects to the kext, sends config data, and begins
listening
for messages from the kext, all from within the notification
callback before
returning, can I count on my driver's validateNewMedia() method not
being
called until after I return from the callback, in the normal
sequence of
events?
Without seeing what you've implemented and having more time than I do
to analyse it, I can't answer this.
You should not, as a general rule, call registerService() until your
driver is in a state where it is ready to be called into immediately.
= Mike
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden