From: "Lee Revell" <rlrevell@joe-job.com>
To: Jiang zhe <zhe.jiang@intel.com>
Cc: tiwai@suse.de, "Tellman, Steven" <Steven.Tellman@idt.com>,
Armando Di Cianno <armando@goodship.net>,
alsa-devel@alsa-project.org
Subject: Re: HDMI v. ICH8 on Dell XPS M1330
Date: Tue, 4 Mar 2008 19:54:58 -0500 [thread overview]
Message-ID: <75b66ecd0803041654x2733bf35pbce849e7bef2ea85@mail.gmail.com> (raw)
In-Reply-To: <1204623862.13915.10.camel@localhost.localdomain>
On Tue, Mar 4, 2008 at 4:44 AM, Jiang zhe <zhe.jiang@intel.com> wrote:
> On Mon, 2008-03-03 at 06:59 +0800, Tobin Davis wrote:
> > It is possible that HDMI audio is pulled from an unknown i2c bus on
> > the
> > video chip. 3dfx did that a long time ago with their 3500 card for
> > their tv tuner portion.
> >
> > I think at this point, unless Steven knows more, this may be
> > unsupported
> > until nVidia adds support in their driver or opens up part of the
> > spec.
> >
> I googled some info about the nvidia G84** or G86** graphics core.
> They got the audio signal from the external audio device through spdif.
>
> For Dell M1330, the spdif configuration for the stac92** codec looks
> well, maybe the graphic driver can control whether the audio signal is
> allowed to transfer through the HDMI port?
In addition to anecdotal evidence, I can confirm that on my work
machine the ATI video driver does seem to touch the audio.
Interestingly it's the userspace X driver, not the in-kernel FGLRX
module.
rlrevell@chronopolis:~$ strings
/usr/lib/xorg/modules/drivers/fglrx_drv.so | grep -i hdmi | grep -i
audio
ex_aHDMIAudioParameters
Isn't DRM fun? ;-)
Lee
next prev parent reply other threads:[~2008-03-05 0:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-27 22:41 HDMI v. ICH8 on Dell XPS M1330 Armando Di Cianno
2008-02-28 11:40 ` Takashi Iwai
2008-02-28 20:55 ` Tellman, Steven
2008-02-29 1:29 ` Armando Di Cianno
2008-02-29 11:56 ` Takashi Iwai
2008-02-29 14:48 ` Tellman, Steven
2008-02-29 14:56 ` Takashi Iwai
2008-02-29 15:04 ` Tellman, Steven
2008-03-02 3:03 ` Lee Revell
2008-03-02 22:20 ` Tellman, Steven
2008-03-02 22:35 ` Armando Di Cianno
2008-03-02 22:59 ` Tobin Davis
2008-03-03 14:50 ` Tellman, Steven
2008-03-03 15:15 ` Takashi Iwai
2008-03-04 9:44 ` Jiang zhe
2008-03-05 0:54 ` Lee Revell [this message]
2008-03-05 15:15 ` Armando Di Cianno
2008-03-05 15:19 ` Armando Di Cianno
2008-03-02 22:36 ` Armando Di Cianno
2008-03-02 22:39 ` Lee Revell
2008-02-29 1:25 ` Armando Di Cianno
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=75b66ecd0803041654x2733bf35pbce849e7bef2ea85@mail.gmail.com \
--to=rlrevell@joe-job.com \
--cc=Steven.Tellman@idt.com \
--cc=alsa-devel@alsa-project.org \
--cc=armando@goodship.net \
--cc=tiwai@suse.de \
--cc=zhe.jiang@intel.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