From: Tobin Davis <tdavis@dsl-only.net>
To: Shaw Terwilliger <sterwill@teamprise.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Intel HDA on Mac Pro
Date: Thu, 07 Dec 2006 06:51:40 -0800 [thread overview]
Message-ID: <1165503100.7530.19.camel@razman> (raw)
In-Reply-To: <457828D7.4020908@teamprise.com>
[-- Attachment #1.1: Type: text/plain, Size: 1102 bytes --]
Sorry, I got a bit backlogged.
I just downloaded the codec spec for the 885, and will start going
through it today. I should have something for you today or tomorrow at
the latest. Since 1.0.14 is now imminent, I need to get cracking on
several fronts and I want to get support for your system and others in
before 1.0.14 final.
Tobin
On Thu, 2006-12-07 at 08:44 -0600, Shaw Terwilliger wrote:
> Shaw Terwilliger wrote:
> >> 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.
>
> Have you had a chance too cook up any patches for the Mac Pro HDA
> hardware? I fooled around with different models yesterday, and the
> "auto" model detects very few output channels (PCM, Front, Line-in), but
> correctly assigns the front channel. It's still incredibly quiet.
>
--
Tobin Davis <tdavis@dsl-only.net>
[-- Attachment #1.2: Type: text/html, Size: 1946 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-07 14:51 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 [this message]
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=1165503100.7530.19.camel@razman \
--to=tdavis@dsl-only.net \
--cc=alsa-devel@lists.sourceforge.net \
--cc=sterwill@teamprise.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