Re: OSX 10.5.6 breaks our user-land driver
Re: OSX 10.5.6 breaks our user-land driver
- Subject: Re: OSX 10.5.6 breaks our user-land driver
- From: Stéphane Letz <email@hidden>
- Date: Wed, 7 Jan 2009 09:03:05 +0100
Message: 1
Date: Tue, 06 Jan 2009 12:00:04 -0800
From: Jeff Moore <email@hidden>
Subject: Re: OSX 10.5.6 breaks our user-land driver...
To: CoreAudio API <email@hidden>
Message-ID: <email@hidden>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes
I can't think of anything that we changed in 10.5.6 in coreaudiod that
would affect your plug-in's ability to bootstrap_look_up something.
But let me be sure what you are asking: Are you saying that your plug-
in instance inside of coreaudiod was calling bootstrap_look_up to look
up a port in a process launched under a user's bootstrap session?
Yes exactly. I understand coreaudiod runs as "root" and jackd server
runs in the user's bootstrap session, but up to now coreaudiod was
able to access the jackd server port.
Has anything changed in how bootstrap contexts are used?
Thanks.
Stephane Letz
On Dec 18, 2008, at 8:08 AM, Stéphane Letz wrote:
With OSX 10.5.6, our user land driver cannot be activated as default
input/output device anymore. It seems that the "coreaudiod" deamon
(that runs under root) cannot connect anymore on our audio server
(jackd) that defines a mach port entry point in the account
bootstrap context. Is this a changed behaviour of coreaudiod deamon
itself? Or any more fundamental change in bootstrap contexts
management in the system?
Jeff Moore
Core Audio
Apple
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden