AZALIA(4) BSD Kernel Interfaces Manual AZALIA(4)NAME
azalia -- Generic High Definition Audio device driver
SYNOPSIS
azalia* at pci? dev ? function ?
audio* at audiobus?
options AZALIA_DEBUG
DESCRIPTION
The azalia device driver is expected to support any PCI device which is compliant to the High Definition Audio Specification 1.0. Known sup-
ported controllers are Intel 82801F (ICH6) and Intel 82801G (ICH7). Known supported codecs are Realtek ALC260, ALC880, ALC882, Analog
Devices AD1981HD, CMedia CMI9880, Sigmatel STAC9221, and STAC9221D.
SEE ALSO audio(4), pci(4) http://www.intel.com/standards/hdaudio/
HISTORY
The azalia device driver appeared in NetBSD 3.0.
BUGS
Non-PCM encodings such as Float32 and AC-3 are not supported.
There is no way to use 20bit or 24bit precision because of a limitation of the MI audio framework.
BSD March 15, 2007 BSD
Check Out this Related Man Page
HDAUDIO(4) BSD Kernel Interfaces Manual HDAUDIO(4)NAME
hdaudio -- High Definition Audio device driver
SYNOPSIS
hdaudio* at pci? dev ? function ?
hdafg* at hdaudiobus?
audio* at audiobus?
options HDAUDIO_DEBUG
options HDAUDIO_AFG_DEBUG
DESCRIPTION
The hdaudio device driver is expected to support any PCI device which is compliant to the High Definition Audio Specification 1.0. It is a
replacement for azalia(4). It was written from scratch following the Intel HD Audio and Microsoft Universal Audio Architecture specifica-
tions.
The driver consists of two interlinked components, which reflects the hardware design. The hdaudio component interfaces with a PCI/PCIe bus
and provides an hdaudiobus(4) onto which different function groups attach. Each function group (e.g. audio, vendor-specific modem) is
exported as a separate child device of the hdaudio controller. Audio function groups (a.k.a. audio codec) are exported as hdafg(4) devices.
Audio codecs are available from a number of manufacturers and are made up of a number of widgets (e.g. audio mixer, output pin, analog-to-
digital converter). The way the widgets are interlinked varies significantly between implementations. The tree of widgets must be parsed
and mapped to mixer(4) controls. As part of this process, loops in the inter-codec links must be detected and muted, bi-directional pins
must be set up appropriately and the locations of pins determined. Unlike the azalia(4) driver (which tends to generate a large number of
unclearly named mixer(4) controls), hdaudio works backwards by starting with a list of desired, consistent and compatible mixer(4) controls
and configuring/discovering appropriate widget link routes to fit.
By following the published mechanisms for common implementations of widget parsing, it is expected that nearly all High Definition Audio
devices will be supported without requiring per-device quirks.
SEE ALSO audio(4), mixer(4), pci(4), hdaudioctl(8), http://www.intel.com/standards/hdaudio/ http://www.microsoft.com/whdc/device/audio/
HISTORY
The hdaudio device driver appeared in NetBSD 5.1.
AUTHORS
The hdaudio driver was written by Jared McNeill <jmcneill@NetBSD.org> under contract by
Precedence Technologies Ltd <http://www.precedence.co.uk/>. The UAA-compliant widget parser is derived from the FreeBSD snd_hda(4) driver.
BUGS
The following items are not yet implemented:
o Improve power management support when driver is idle
o Add support for non-PCM output formats
o Handle unsolicited RIRB messages
o Modem function groups
BSD September 28, 2010 BSD
I have just bought a new HP Pavilion dv7 notebook (17", AMD Turion) and installed Fedora Core 10. I would like to add that i installed a completely eyecandy-less base system, only then installed a naked x-org Xserver and mwm (Motif Window Manager) on top of it. There is neither KDE nor GNOME nor... (2 Replies)
I reformatted my hard drive and installed Mandriva 2011.
It works fine. I can go to the Internet
The problem is no sound.
I want to listen to songs from YouTube. Sound doesn't come.
I see a man is singing on the screen. No sound.
I had no problem with my old Mandriva. Sound and everything... (11 Replies)
In a case of root=/dev/ram0 real_root=/dev/sda2
No filesystem could mount root, tried: ext3 ext2...
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0)
http://imageplay.net/img/tya22288136/IMG0204A.jpg (real_root - real panic)
The case of omitting real_root and... (1 Reply)