From: Takashi Iwai <tiwai@suse.de>
To: German Gomez Garcia <german@piraos.com>
Cc: alsa mailing list <Alsa-devel@lists.sourceforge.net>
Subject: Re: SBLive SPDIF output under SMP.
Date: Wed, 20 Feb 2002 10:24:29 +0100 [thread overview]
Message-ID: <s5hr8ngwlo2.wl@alsa2.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0202190116450.2045-100000@hal9000.piraos.com>
At Tue, 19 Feb 2002 01:21:10 +0100 (CET),
German Gomez Garcia wrote:
>
> Hello,
>
> I would like to know if S/PDIF output of AC3 frames is supported
> in the ALSA emu10k1 driver under SMP, I was unable to make it work, I've
> tried ac3play (from alsaplayer) and latest ALSA CVS and also opensource
> emu10k1 driver and the play-ac3 utils that comes with it. I have a
> Cambridge Soundworks DTT2500 external Dolby Digital decoder, when I load
> the emu10k1 opensource driver I get the following info about my SBLive
> card:
>
> Creative EMU10K1 PCI Audio Driver, version 0.18, 00:59:28 Feb 19 2002
> EMU10K1 rev 5 model 0x8040 found, IO at 0x1800-0x181f, IRQ 19
> ac97_codec: AC97 Audio codec, id: 0x8384:0x7609 (SigmaTel STAC9721/23)
>
> It's a SBLive Platinum (with the LiveDrive II) and I'm connecting the
> DTT2500 to the LiveDrive II's coaxial spdif output.
>
> I'm running it on a dual Athlon 1.4 Thunderbird in a Tyan TigerMP,
> any ideas??
Doesn't this happen when you start with UP?
Did you enable HIGHMEM or 1GB config in your kernel?
This might affect the behavior (yesterday I saw a report that without
highmem option AC3 worked).
ciao,
Takashi
_______________________________________________
Alsa-devel mailing list
Alsa-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-devel
prev parent reply other threads:[~2002-02-20 9:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-19 0:21 SBLive SPDIF output under SMP German Gomez Garcia
2002-02-20 9:24 ` Takashi Iwai [this message]
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=s5hr8ngwlo2.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=Alsa-devel@lists.sourceforge.net \
--cc=german@piraos.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.