From: Arun Raghavan <arun.raghavan@collabora.co.uk>
To: alsa-devel@alsa-project.org
Subject: CS4206 and S/PDIF (again)
Date: Tue, 01 Mar 2011 10:36:09 +0530 [thread overview]
Message-ID: <1298955969.12314.12.camel@snowflake> (raw)
Hello,
I saw an earlier thread where someone with a MacBook Pro 6.2 couldn't
get S/PDIF working. I'm facing the same problem on my MacBook Pro 5.5. I
know this used to work at some point because the LED from the digital
out used to glow (but my last recollection of this is from ca. Jan 2010,
so not too helpful).
I tried jiggling some controls in hda-analyzer, but I don't yet know
enough about this to be sure what I was doing made any sense.
I've uploaded alsa-info [1] and codecgraph [2] outout, and would really
appreciate help figuring out how I can go about debugging this problem.
[1] http://people.collabora.co.uk/~arun/alsa-info.txt
[2] http://people.collabora.co.uk/~arun/cs4206-mbp55.svg
Cheers,
Arun
p.s.: fwiw, I'm testing with a: aplay -v -D iec958:CARD=NVidia,DEV=0
SURROUNDTEST_011212.wav
next reply other threads:[~2011-03-01 5:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 5:06 Arun Raghavan [this message]
2011-03-01 5:43 ` CS4206 and S/PDIF (again) Arun Raghavan
2011-03-01 5:43 ` Arun Raghavan
2011-03-02 21:48 ` Arun Raghavan
2011-03-02 21:48 ` [PATCH] ALSA: hda - apply CS420X erratum fix for CS4207 only Arun Raghavan
2011-03-02 22:03 ` Austin, Brian
2011-03-03 4:58 ` Mohammad Bahathir Hashim
2011-03-03 5:27 ` Arun Raghavan
2011-03-03 12:01 ` Takashi Iwai
2011-03-03 12:20 ` Arun Raghavan
2011-03-03 13:58 ` Takashi Iwai
2011-03-03 14:07 ` Arun Raghavan
2011-03-03 14:20 ` Takashi Iwai
2011-03-03 18:49 ` Austin, Brian
2011-03-04 7:26 ` Takashi Iwai
2011-03-03 14:13 ` Mohammad Bahathir Hashim
2011-03-02 22:02 ` CS4206 and S/PDIF (again) Austin, Brian
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=1298955969.12314.12.camel@snowflake \
--to=arun.raghavan@collabora.co.uk \
--cc=alsa-devel@alsa-project.org \
/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;
as well as URLs for NNTP newsgroup(s).