[alsa-devel] ALC268 auto-parsing
tdavis at dsl-only.net
Wed Jan 16 19:26:41 CET 2008
It really depends on the OEM platform. Some are good about putting the
correct config in bios, others not so good. If your system is listed
specifically in one of the inf files for the windows driver, you are in
this second category (look for the pci subdevice ID or the codec
Now, the problem with the Windows INF files is that they use the Windows
GUID method for programming registers. This is essentially a text
encryption method that makes it user unreadable. Sigmatel is the only
vendor I know of that supplies the register settings in human readable
format, but even it has limits to what is usable to make a Linux driver.
The bios configuration is the Microsoft portion of the HDA standard.
This way, basic audio functionality works out of the box. Most codec
vendors want to give the user better control, hence the need for
specific drivers and utilities. We try to give the user some level of
flexibility based on what makes sense (i.e. green plug for front
speakers, etc), but it is technically feasable to have any plug support
multiple functions (using the front Mic jack as a second headphone plug
for example), so long as the codec can handle the desired configuration.
Most of the audio codec vendors for HD Audio have their codec reference
guides online. Realtek in particular are good to work with.
Hope this is helpful.
On Wed, 2008-01-16 at 18:48 +0100, Marco Schuster wrote:
> Hi all,
> I am a bit interested in how the Realtek Windows driver gets its pin
> config. There IMO are two options:
> a) it uses the bios autoconfig - as parsing this doesn't work in alsa
> here, there must be something special in it
> b) it uses a config file - it should be easy to get out the pin config.
> Any opinions what is correct way?
> Alsa-devel mailing list
> Alsa-devel at alsa-project.org
How much of their influence on you is a result of your influence on them?
More information about the Alsa-devel