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: Mon, 11 Dec 2006 10:52:44 -0600 [thread overview]
Message-ID: <457D8CDC.4090501@sourcegear.com> (raw)
In-Reply-To: <1165854833.7530.205.camel@razman>
[-- Attachment #1.1: Type: text/plain, Size: 996 bytes --]
lineTobin Davis wrote:
> Ok, based on that information, I think I have a working patch. Give
> this a try.
>
> I'll let the next guy work on the S/PDIF if there is an issue with it.
I get no sound from my speakers at all with this patch (via aplay,
speaker-test, etc.). Here's the dmesg from load:
[601946.977991] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 23 (level,
low) -> IRQ 225
[601946.978931] PCI: Setting latency timer of device 0000:00:1b.0 to 64
[601947.011648] ALSA
/data/downloads/alsa-driver-1.0.14rc1/pci/hda/../../alsa-kernel/pci/hda/hda_intel.c:696:
codec_mask = 0x1
[601947.196396] ALSA
/data/downloads/alsa-driver-1.0.14rc1/pci/hda/hda_codec.c:1743:
hda_codec: model 'macpro' is selected
The mixer shows the following playback channels:
PCM
Front
Line-in
PC Speakers
I even tried the front headphone jack with the speaker test and toggled
the headphone switch. No sound.
--
Shaw Terwilliger <sterwill@sourcegear.com>
SourceGear LLC
[-- 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
next prev parent reply other threads:[~2006-12-11 16:52 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
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 [this message]
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=457D8CDC.4090501@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