From: Tobin Davis <tdavis@dsl-only.net>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: trying to get sound working at a mac book pro (core 2 duo)
Date: Wed, 14 Feb 2007 17:13:20 -0800 [thread overview]
Message-ID: <1171502000.7083.23.camel@razman.gruemaster.com> (raw)
In-Reply-To: <s5hire4l6ho.wl%tiwai@suse.de>
[-- Attachment #1.1: Type: text/plain, Size: 728 bytes --]
On Wed, 2007-02-14 at 23:27 +0100, Takashi Iwai wrote:
> The driver always takes PCI SSID as a key for table-lookup.
> The codec has its own SSID (and often a different value from PCI SSID)
> as proc shows, but it's not used anywhere in the driver code.
>
>
This is the second time I've run into a system that has an HD audio
chip, but doesn't have a unique PCI SSID. The first was the Mac Pro,
where there is no SSID for the HD audio bus (see my patch for ALC885 Mac
Pro - 12/15).
Takashi, we may want to look into a function that uses the codec
subsystem id as a fallback, with the PCI SSID taking precedence. We
already detect the HD Audio bus, through the PCI ID. Let me know.
--
Tobin Davis <tdavis@dsl-only.net>
[-- Attachment #1.2: Type: text/html, Size: 1305 bytes --]
[-- Attachment #2: Type: text/plain, Size: 345 bytes --]
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
[-- Attachment #3: Type: text/plain, Size: 161 bytes --]
_______________________________________________
Alsa-devel mailing list
Alsa-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-devel
next prev parent reply other threads:[~2007-02-15 1:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-14 19:21 trying to get sound working at a mac book pro (core 2 duo) Rafael Espíndola
2007-02-14 19:40 ` Tobin Davis
[not found] ` <564d96fb0702141209g6b032115pebe2ce1a7e3de57b@mail.gmail.com>
2007-02-14 20:11 ` Fwd: " Rafael Espíndola
2007-02-14 20:13 ` Rafael Espíndola
2007-02-14 20:35 ` Rafael Espíndola
2007-02-14 20:56 ` Rafael Espíndola
2007-02-14 22:27 ` Takashi Iwai
2007-02-14 22:32 ` Rafael Espíndola
2007-02-15 1:13 ` Tobin Davis [this message]
2007-02-15 12:12 ` Takashi Iwai
2007-02-15 19:55 ` Rafael Espíndola
2007-02-15 20:58 ` tdavis
2007-02-16 12:30 ` Takashi Iwai
2007-02-17 14:42 ` Rafael Espíndola
2007-02-18 13:19 ` Rafael Espíndola
2007-02-15 10:39 ` Rafael Espíndola
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1171502000.7083.23.camel@razman.gruemaster.com \
--to=tdavis@dsl-only.net \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.