From: Tobin Davis <tdavis@dsl-only.net>
To: Shaw Terwilliger <sterwill@sourcegear.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Intel HDA on Mac Pro
Date: Mon, 04 Dec 2006 16:30:02 -0800 [thread overview]
Message-ID: <1165278602.32312.110.camel@razman> (raw)
In-Reply-To: <4574BB17.1020807@sourcegear.com>
[-- Attachment #1.1: Type: text/plain, Size: 1098 bytes --]
On Mon, 2006-12-04 at 18:19 -0600, Shaw Terwilliger wrote:
> I've verified that lspci doesn't show any subsystems for the HDA device.
> It does show (known) subsystems for other devices (USB, SATA, IDE, etc.).
>
This is strange. Could you try 'lspci -s 0:1b -vv"? It should have
something there, but maybe not.
> Kernel messages are from 1.0.13 with --with-debug=full:
>
I had thought you compiled with "--with-debug=detect". This actually
gives different output than full debug mode.
> Earlier today with no model arg present, I unmuted and maxed out all the
> mixer channels, and found that with PCM and Surround channels all the
> way up, and external amplifier up, I could hear the music I had playing,
> though it was still very quiet. So at least one channel is finding the
> line-out jack, quietly.
This is actually good info. Interesting that sound is coming out from
the Surround channels. The low volume could mean that EAPD still needs
to be set.
I'll look more into this tomorrow. Hopefully I can get a patch for you
to test.
--
Tobin Davis <tdavis@dsl-only.net>
[-- Attachment #1.2: Type: text/html, Size: 1903 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-05 0:30 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 [this message]
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
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=1165278602.32312.110.camel@razman \
--to=tdavis@dsl-only.net \
--cc=alsa-devel@lists.sourceforge.net \
--cc=sterwill@sourcegear.com \
/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