From: Takashi Iwai <tiwai@suse.de>
To: Benny Sjostrand <gorm@cucumelo.org>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: [PATCH] cs46xx, SPDIF output fixes, AC3 through IEC958 should work OK
Date: Mon, 03 Mar 2003 12:33:58 +0100 [thread overview]
Message-ID: <s5hof4slm55.wl@alsa2.suse.de> (raw)
In-Reply-To: <3E62AEEF.7090109@cucumelo.org>
At Mon, 03 Mar 2003 02:25:03 +0100,
Benny Sjostrand wrote:
>
> [1 <text/plain; us-ascii (7bit)>]
> Hi!
>
> With this patch AC3 through IEC958 should work OK, and synchronizations
> problems with the SPDIF output should be gone. (about SPDIF input the
> status is still the same)
>
> I've tested it with ogle 0.9, the AC3 stuff seems to work well, have
> not tested with xine (yet).
>
> This patch adds a new DSP firmware routine, that makes it's possible to
> DMA from host directly to the SPDIF output. This will affect all
> playback on IEC958 device on 48khz, other rates will (should) work
> exactly as before.
>
> - Added the cwcdma DSP firmware module
> - Fixed a minor bug in cs46xx_iec958_pre_open(...)
> - in cs46xx_dsp_enable_spdif_hw(...), disable SPDIF hw
> before enabling, this seems to help solving the synchronization issue
> - Some changes in cs46xx_dsp_create_pcm_channel(...) and
> cs46xx_dsp_create_src_task_scb(...) to adapt to the new DSP firmware.
>
> Well, with the new firmware module I would consider this patch a little
> bit experimental ;)
thanks, applied to cvs.
it's working fine on my DMX x-fire 1024.
Takashi
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2003-03-03 11:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-03 1:25 [PATCH] cs46xx, SPDIF output fixes, AC3 through IEC958 should work OK Benny Sjostrand
2003-03-03 11:33 ` Takashi Iwai [this message]
2003-03-03 14:08 ` Benny Sjostrand
2003-03-03 13:07 ` Takashi Iwai
2003-03-05 0:58 ` Christian Esken
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=s5hof4slm55.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=gorm@cucumelo.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 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.