All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Alex Song <asong@xvdcorp.com>
Cc: "'alsa-devel@lists.sourceforge.net'" <alsa-devel@lists.sourceforge.net>
Subject: Re: ATI IXP SPDIF
Date: Tue, 25 May 2004 11:44:44 +0200	[thread overview]
Message-ID: <s5hhdu4x2lv.wl@alsa2.suse.de> (raw)
In-Reply-To: <1649E0C057D17842BA917E5124BF331A15BD7A@as2.alaris.com>

At Mon, 24 May 2004 16:16:42 -0700,
Alex Song wrote:
> 
> hi,
> 
> i am trying to get SPDIF output working on ATI IXP/Realtek ALC655 and i am
> using atiixp.c from cvs (version 1.9) and linux kernel 2.6.5. i tried
> playing back wav files through aplay and ac3 files with ac3play and i
> couldn't get any output from either SPDIF over AC97 or SPDIF Direct. analog
> output is fine. from the cvs logs i gather that SPDIF on ATI IXP should work
> for some cases at least, has anyone got it to work? if so with what
> files/hardware/settings etc?

it works fine on my test machine.  it's an ASUS mobo (forgot the
model).

	% ac3dec -C some-48k.ac3

or

	% aplay -Dplug:spdif foo.wav

but the direct SPDIF mode doesn't work...

--
Takashi Iwai <tiwai@suse.de>		ALSA Developer - www.alsa-project.org


-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. 
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click

  reply	other threads:[~2004-05-25  9:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-24 23:16 ATI IXP SPDIF Alex Song
2004-05-25  9:44 ` Takashi Iwai [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-05-26 22:19 Alex Song
2004-05-27 12:45 ` Takashi Iwai
2004-05-27 19:17 Alex Song

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=s5hhdu4x2lv.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=asong@xvdcorp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.