Re: CVS Web Availability
Re: CVS Web Availability
- Subject: Re: CVS Web Availability
- From: Laurent Cerveau <email@hidden>
- Date: Tue, 27 Nov 2001 22:18:30 +0100
On Tuesday, November 27, 2001, at 10:01 PM, Sean Morrell wrote:
Oh! That's right. Sorry. Well is the source code to HAL available?
You mentioned in a previous message: "On the Kernel side you would have
created appropriate IOAudio controls and in the plugin you would do
exactly like the HAL does : parse the registry for these and do the
changes.".
If the HAL source is not open, is there some other code that would help
me
in understanding how the HAL parses the registry for IOAudio controls,
and
how the plugin will set the values?
I have read I/O Kit Fundamentals and browsed the I/O Kit API Reference?
Is IORegistryEntry what I need to parse the registry? Is there any
additional documentation on the I/O Registry other than what I
mentioned?
In this case you are in user land (in a CF bundle) , so what you will
not use the IOKit C++ objects but the C API from user land. Habe a look
at the pdf "Accessing Hardware form Application" it should be pretty
helpful.
http://developer.apple.com/techpubs/macosx/Darwin/IOKit/DeviceInterfaces/AccessingHardware.
pdf
Also, should I be able to see the various audio properties, controls,
etc
in IORegistryExplorer? Because I don't?
Yes you see them : for example for the built in you will look for
AppleScreamerAudio, or AppleBurgundyAudio or AppleDacaAudio, or
AppleTexasAudio (depending on the machine you are using and the Codec on
it). If you are in the IOService plane you'll see all the controls and
their properties (IOAudioLevelControl, and so on...). There is a search
facility in IOregistry Explorer that you can use.
Otherwise you can do in Terminal : ioreg | grep Audio to find the Audio
nodes, and then ask for their properties with the -n option.
Laurent
Laurent Cerveau
Applications Division
Apple Computer Inc.
email@hidden