On Wed, 2007-12-26 at 21:30 -0500, Lee Revell wrote:
On Dec 26, 2007 7:47 PM, Tobin Davis tdavis@dsl-only.net wrote:
Ok, the second codec is the HDMI port. For some reason, it is getting assigned to be primary sound device. Try "alsamixer -D hw:1.0" to see if it can control the realtek device.
Oddly enough, I used to work at Intel as a contractor, developing audio drivers for their boards. They stopped supporting Linux when my contract ended.
Just curious - is there really anything Intel could do at this point to improve the snd-hda-intel situation? My impression is that their decision to architect the thing such that every vendor can wire things up their own way (or "add value" in marketing speak) is the root of the support nightmare that these devices are.
It seems that the only way to improve things would be to either get every single PC vendor to help, or make the pin configs settable from userspace and develop a tool to translate from the vendor provided Windows .inf files.
Do I grok the situation correctly?
Close. Actually, the snd-hda-intel protocol is something that Intel & Microsoft cobbled together. Ideally, there would be a general purpose driver for the audio bus, and a user space application that would configure it. Takashi, myself, and a couple of other developers are exploring this method currently, but with the major influx of new systems, it's been hard to keep up and develop a new api. We hope to get into a beta for 2.6.26 kernel release. Keep watching the email threads.