Re: Audio driver outside kernel
Re: Audio driver outside kernel
- Subject: Re: Audio driver outside kernel
- From: Brian Willoughby <email@hidden>
- Date: Mon, 7 Nov 2005 15:05:06 -0800
Perhaps some clarification is in order:
kernel code is more difficult to write than user code, at least in general.
When it comes to an audio driver, the norm is reversed. That's because there
is a substantial support library for a kernel-based audio driver, and nothing
for the user-land audio driver.
(sorry for being pedantic, it just seemed so funny to read that writing in the
kernel is much easier that writing in user land!)
Brian Willoughby
Sound Consulting
Begin forwarded message:
On Nov 7, 2005, at 1:02 PM, try another wrote:
> I was told that the only way to write a CoreAudio driver was via a
> kext.
That is the preferred and easiest way to write an audio driver. This
is the way to go for just about every audio device out there. There
are precious few cases where it makes sense to take on the added
complexity of writing a user-land driver makes sense versus doing the
easy thing by writing a kernel driver.
> So I can write a user-land driver for an audio "device" using the
> <CoreAudio/AudioHardwarePlugIn.h> API?
Yes, but be aware that this is not the easiest thing to do correctly.
There is no sample code or documentation save what's in the header.
Given that your driver is basically on it's own for implementing the
semantics of the HAL, this is definitely not the path of least
resistance.
> Thanks,
> This is really good news.
I don't know that I'd say that. Writing a user-land driver is several
orders of magnitude more difficult than writing a kernel driver and
such devices cannot be aggregated. So generally, you're better served
by writing a kernel driver.
--
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