From: Nicolas Boichat <nicolas@boichat.ch>
To: Takashi Iwai <tiwai@suse.de>
Cc: Matt Porter <mporter@embeddedalley.com>,
alsa-devel@lists.sourceforge.net, Rene Rebe <rene@exactcode.de>
Subject: Re: ALSA Intel HDA MacBook
Date: Sun, 23 Jul 2006 16:31:17 +0200 [thread overview]
Message-ID: <44C38835.6010200@boichat.ch> (raw)
In-Reply-To: <s5hk66k76sh.wl%tiwai@suse.de>
Hi,
Takashi Iwai wrote:
>
> OK then it's somewhat another black magic :)
>
> Linus made a patch to make MacMini to work. The patch is below (and
> it's already merged to ALSA HG tree, too).
> Could you check whether it works for other Intel Mac models?
> At least, we need to check that it doesn't break something...
>
I finally found the time to test this patch on my Macbook Pro (I'm
running 2.6.18-rc2, which includes this patch).
I have the following results:
- "Side" controls internal speakers, if no headphone is plugged
- "Front" controls headphones
- Line-in is always set as output ("Line In as output" has no effect),
"Center" controls line-"out" left channel, "LFE" the right channel.
- "Surround" has no effect.
However, the internal mic doesn't work anymore (whatever value I put in
"Capture", "Input Source" and "Mux")...
Best regards,
Nicolas
>
> Subject: x86 MacMini: make built-in speaker sound actually work
>
> The MacMini board table seems to largely look like any bog-standard
> Intel 945 board.
>
> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
>
> ---
> commit 7c3dec0679c66ce177726802adbe2f403942fc27
> tree 62d286f0b477a62d6996b6ba2cacdc3cdd4579a9
> parent c80dc60b03d633047c7f96be87fd59cdcdbb929f
> author Linus Torvalds <torvalds@macmini.osdl.org> Mon, 10 Jul 2006 22:21:43 -0700
> committer Linus Torvalds <torvalds@macmini.osdl.org> Mon, 10 Jul 2006 22:21:43 -0700
>
> sound/pci/hda/patch_sigmatel.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/sound/pci/hda/patch_sigmatel.c b/sound/pci/hda/patch_sigmatel.c
> index fb4bed0..ea99083 100644
> --- a/sound/pci/hda/patch_sigmatel.c
> +++ b/sound/pci/hda/patch_sigmatel.c
> @@ -351,6 +351,7 @@ static unsigned int *stac922x_brd_tbl[ST
> [STAC_REF] = ref922x_pin_configs,
> [STAC_D945GTP3] = d945gtp3_pin_configs,
> [STAC_D945GTP5] = d945gtp5_pin_configs,
> + [STAC_MACMINI] = d945gtp5_pin_configs,
> [STAC_D965_2112] = d965_2112_pin_configs,
> };
>
>
-------------------------------------------------------------------------
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
next prev parent reply other threads:[~2006-07-23 14:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200607081323.17265.rene@exactcode.de>
[not found] ` <200607081354.33539.rene@exactcode.de>
2006-07-08 19:20 ` ALSA Intel HDA MacBook Rene Rebe
2006-07-08 20:36 ` Maya Falmagne
2006-07-08 20:38 ` Lee Revell
2006-07-10 10:32 ` Takashi Iwai
2006-07-10 11:44 ` Rene Rebe
2006-07-10 12:00 ` Nicolas Boichat
2006-07-11 10:52 ` Takashi Iwai
2006-07-16 15:37 ` Rene Rebe
2006-07-23 14:31 ` Nicolas Boichat [this message]
2006-07-28 13:19 ` Matt Porter
2006-07-28 13:21 ` Takashi Iwai
2006-07-28 19:00 ` Nicolas Boichat
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=44C38835.6010200@boichat.ch \
--to=nicolas@boichat.ch \
--cc=alsa-devel@lists.sourceforge.net \
--cc=mporter@embeddedalley.com \
--cc=rene@exactcode.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox