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: Mon, 04 Dec 2006 22:02:58 -0600	[thread overview]
Message-ID: <4574EF72.8020207@sourcegear.com> (raw)
In-Reply-To: <1165278602.32312.110.camel@razman>


[-- Attachment #1.1: Type: text/plain, Size: 2578 bytes --]

alsa-devel@lists.sourceforge.netTobin Davis wrote:
> This is strange.  Could you try 'lspci -s  0:1b -vv"?  It should have
> something there, but maybe not.

00:1b.0 Audio device: Intel Corporation Enterprise Southbridge High
Definition Audio (rev 09)
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR-
	Latency: 0, Cache Line Size: 256 bytes
	Interrupt: pin A routed to IRQ 225
	Region 0: Memory at 92f00000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: [50] Power Management version 2
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA
PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [60] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
		Address: 0000000000000000  Data: 0000
	Capabilities: [70] Express Unknown type IRQ 0
		Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag-
		Device: Latency L0s <64ns, L1 <1us
		Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
		Device: RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop+
		Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
		Link: Supported Speed unknown, Width x0, ASPM unknown, Port 0
		Link: Latency L0s <64ns, L1 <1us
		Link: ASPM Disabled CommClk- ExtSynch-
		Link: Speed unknown, Width x0

>> 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.

I changed it to "full" later to see if I got any more info.  Here they
are again with --with-debug=detect (4 Xeon cores makes ALSA compiles fly
by):

modprobe snd-hda-intel:
[37954.257842] ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 23 (level,
low) -> IRQ 225
[37954.258700] PCI: Setting latency timer of device 0000:00:1b.0 to 64
[37954.291651] ALSA
/data/downloads/alsa-driver-1.0.13/pci/hda/../../alsa-kernel/pci/hda/hda_intel.c:680:
codec_mask = 0x1
[37954.471856] ALSA
/data/downloads/alsa-driver-1.0.13/pci/hda/hda_codec.c:1756: hda_codec:
PCI 0:0, codec config 0 is selected

> 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.

Thanks for all your help.  I'm happy to test any patches you come up with.

-- 
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

  reply	other threads:[~2006-12-05  4:02 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 [this message]
     [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=4574EF72.8020207@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