From: "Andreas Nüßlein" <nutz@unfoog.de>
To: alsa-devel@alsa-project.org
Subject: Re: No sound with nVidia Corporation MCP79 High Definition Audio (rev b1) (Macbook Pro 5, 5)
Date: Wed, 1 Jul 2009 17:00:42 +0200 [thread overview]
Message-ID: <200907011700.43178.nutz@unfoog.de> (raw)
In-Reply-To: <s5heit2i7pi.wl%tiwai@suse.de>
so i tried to find some information in OS X and after a while i stumbled upon a
document "Info.plist", to which i was pointed by OS X's build-in hardware
info-utility, somehwere in /System/Library/Extensions/AppleHDA.kext/....
http://nopaste.org/p/aRCCwdDXqb
also some information right out of the apple tool, eventhough i don't think
that it's worth anything:
Intel High Definition Audio:
Device ID: 0x10DECB79
Audio ID: 77
Available Devices:
Headphone:
Connection: Combo
Speaker:
Connection: Internal
Line In:
Connection: Combo
Internal Microphone:
Connection: Internal
S/P-DIF Out:
Connection: Combo
External Microphone:
Connection: Combo
On Tuesday 30 June 2009 07:58:17 Takashi Iwai wrote:
> At Mon, 29 Jun 2009 16:04:06 -0600,
>
> Sean Burke wrote:
> > A quick google shows that the vendor ID is Cirrus Logic. The Boot Camp
> > driver set does include installers for Cirrus audio cards. I don't have
> > Windows installed on here, so I can't check to see if it is indeed the
> > Cirrus drivers that get installed. What can be done to facilitate the
> > implementation of this codec?
>
> I guess it's CS4206 codec. CS4207 has a different id.
out of the Info.plist:
<string>Cirrus Logic CS4206</string>
<key>CodecID</key>
so again: if i can, i'd love to help.
thanks a lot
next prev parent reply other threads:[~2009-07-01 15:00 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 22:04 No sound with nVidia Corporation MCP79 High Definition Audio (rev b1) (Macbook Pro 5, 5) Sean Burke
2009-06-30 5:58 ` Takashi Iwai
2009-07-01 15:00 ` Andreas Nüßlein [this message]
2009-07-02 9:45 ` Takashi Iwai
2009-07-02 10:54 ` Andreas Nüßlein
2009-07-02 10:57 ` Takashi Iwai
2009-07-02 13:15 ` Takashi Iwai
2009-07-02 17:37 ` Andreas Nüßlein
2009-07-03 5:37 ` Takashi Iwai
2009-07-03 11:25 ` Andreas Nüßlein
2009-07-03 13:15 ` Takashi Iwai
[not found] ` <200907061459.09745.nutz@unfoog.de>
[not found] ` <s5hy6r2exs2.wl%tiwai@suse.de>
2009-07-06 14:03 ` Andreas Nüßlein
2009-07-06 14:16 ` Takashi Iwai
[not found] ` <200907061636.10288.nutz@unfoog.de>
2009-07-06 14:47 ` Takashi Iwai
[not found] ` <200907061703.52699.nutz@unfoog.de>
2009-07-06 15:13 ` Takashi Iwai
[not found] ` <200907061723.18123.nutz@unfoog.de>
2009-07-06 15:43 ` Takashi Iwai
[not found] ` <200907061753.47013.nutz@unfoog.de>
2009-07-06 16:12 ` Takashi Iwai
2009-07-06 17:16 ` Sean Burke
2009-07-06 19:26 ` Takashi Iwai
[not found] ` <200907062214.56736.nutz@unfoog.de>
2009-07-07 6:00 ` Takashi Iwai
[not found] ` <4A52EA33.1090808@gmail.com>
2009-07-07 6:38 ` Takashi Iwai
2009-07-07 9:47 ` Takashi Iwai
[not found] ` <200907071149.57736.nutz@unfoog.de>
2009-07-07 10:53 ` Takashi Iwai
2009-07-08 14:49 ` Takashi Iwai
[not found] ` <200907081811.29710.nutz@unfoog.de>
2009-07-09 7:18 ` Takashi Iwai
2009-07-10 0:27 ` Andreas Nüßlein
2009-07-10 0:29 ` Andreas Nüßlein
2009-07-16 13:49 ` Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
2009-06-27 1:16 Andreas Nuesslein
2009-06-29 7:24 ` Takashi Iwai
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=200907011700.43178.nutz@unfoog.de \
--to=nutz@unfoog.de \
--cc=alsa-devel@alsa-project.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox