Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Shaw Terwilliger <sterwill@sourcegear.com>
To: Tobin Davis <tdavis@dsl-only.net>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Intel HDA on Mac Pro
Date: Fri, 08 Dec 2006 13:39:12 -0600	[thread overview]
Message-ID: <4579BF60.8000601@sourcegear.com> (raw)
In-Reply-To: <1165535200.7530.63.camel@razman>


[-- Attachment #1.1.1: Type: text/plain, Size: 1894 bytes --]

Tobin Davis wrote:
> To test it, start with either the alsa-driver-hg20061130.tar.bz2 or
> download the recent 1.0.14rc1 and follow these instructions:
> tar -jxvf alsa-driver-<version>.tar.bz2   # <version> == hg20061130 or
> 1.0.14rc1
> cd alsa-driver-<version>/alsa-kernel
> patch -p1 <macpro.patch.1
> cd ..
> ./configure --with-cards=hda-intel --with-debug=detect ; make ; make install
> dmesg -c
> modprobe -r snd-hda-intel
> modprobe snd-hda-intel model=macpro
> dmesg >dmesg.out

Patch applies cleanly and builds with 1.0.14rc1, and macpro model
selection works.  The dmesg dump is attached (though it's pretty terse).

> Send me a copy of dmesg.out along with any differences that you see.  I
> may need to tweak which pins get enabled.

Great news: I have the correct volume!  Here are some mixer oddities:

- The "Surround" mixer channels actually control what comes out of the
line-out jack on the back of the Mac Pro (where I have my speakers
plugged in).  This was the case before.

- The "Front Mic" mixer channels actually control the line-in jack on
the back of the Mac Pro (where I have my radio's line-out plugged in).

- No combination of mixer channel volumes and "Headphone" switch setting
seems to control the headphone jack on the front of the Mac Pro (can't
get any sound from it).  Not a big deal for me, but might be for others.

- The "PC Speaker" mixer channel doesn't control the internal speaker.
I don't know if this is actually possible in OS X (don't have it installed).

Also, I don't have an optical cable to test the digital in/out.  Have
not tested the other analog channels (don't have a mic, etc.).

Thanks for your work fixing up the driver for the 885.

-- 
Shaw Terwilliger <sterwill@teamprise.com>
Teamprise LLC
http://teamprise.com/



-- 
Shaw Terwilliger <sterwill@sourcegear.com>
SourceGear LLC

[-- Attachment #1.1.2: model-macpro.dmesg.out --]
[-- Type: text/plain, Size: 408 bytes --]

[352334.966359] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 23 (level, low) -> IRQ 225
[352334.967289] PCI: Setting latency timer of device 0000:00:1b.0 to 64
[352335.000095] ALSA /data/downloads/alsa-driver-1.0.14rc1/pci/hda/../../alsa-kernel/pci/hda/hda_intel.c:696: codec_mask = 0x1
[352335.177917] ALSA /data/downloads/alsa-driver-1.0.14rc1/pci/hda/hda_codec.c:1743: hda_codec: model 'macpro' is selected

[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]

[-- Attachment #2: Type: text/plain, Size: 347 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

  reply	other threads:[~2006-12-08 19:39 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-04 20:34 Intel HDA on Mac Pro Shaw Terwilliger
2006-12-04 20:51 ` Tobin Davis
2006-12-04 21:02   ` Shaw Terwilliger
2006-12-04 23:45     ` Tobin Davis
2006-12-05  0:19       ` Shaw Terwilliger
2006-12-05  0:30         ` Tobin Davis
2006-12-05  4:02           ` Shaw Terwilliger
     [not found]             ` <457828D7.4020908@teamprise.com>
2006-12-07 14:51               ` Tobin Davis
2006-12-07 23:46               ` Tobin Davis
2006-12-08 19:39                 ` Shaw Terwilliger [this message]
2006-12-10 16:16                   ` Tobin Davis
2006-12-11 14:43                     ` Shaw Terwilliger
2006-12-11 16:33                       ` Tobin Davis
2006-12-11 16:52                         ` Shaw Terwilliger
2006-12-11 17:05                           ` Tobin Davis
2006-12-11 17:13                             ` Shaw Terwilliger
2006-12-11 17:43                               ` Tobin Davis
2006-12-11 19:09                                 ` Shaw Terwilliger
2006-12-11 22:10                 ` Richard
2006-12-11 22:55                   ` Tobin Davis
     [not found]                     ` <f0d712d60612111704x14717093p6e038641fc6e94e6@mail.gmail.com>
2006-12-13 15:22                       ` Tobin Davis
2006-12-13 16:36                         ` Shaw Terwilliger
2006-12-13 17:11                           ` Tobin Davis
2006-12-14  7:01                           ` Tobin Davis
2006-12-14 15:10                             ` Shaw Terwilliger
2006-12-14 16:51                               ` Tobin Davis
2006-12-14 21:24                                 ` Shaw Terwilliger
2006-12-15  2:28                                   ` Tobin Davis

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=4579BF60.8000601@sourcegear.com \
    --to=sterwill@sourcegear.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=tdavis@dsl-only.net \
    /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