Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: joy <joy@pingfm.org>
To: alsa-devel@lists.sourceforge.net
Subject: Re: spdif-trough and snd_ctl_elem_*
Date: Thu, 18 Jul 2002 00:31:16 +0200	[thread overview]
Message-ID: <20020717223116.GA3310@pingfm.org> (raw)
In-Reply-To: <s5hptxm8rs9.wl@alsa2.suse.de>

On Wed, Jul 17, 2002 at 02:25:58PM +0200, Takashi Iwai wrote:
> the implementation of controls for iec958 is fairly dependent on each
> card.  some card needs more initialization and some not.  it's true
> that this might be confusing if you want to access such switches
> _directly_.
> 
> on alsa, instead of tweaking these lowlevel stuffs, you can use an
> abstraction pcm layer.
> typically, the pcm "iec958" (or "spdif" equivalently) does all such a
> job.  the iec958 pcm accepts arguments which represent status bytes.
> 
> 	iec958:AES0=0xXXXX,AES1=0xXXXX,AES2=0xXXXX,AES3=0xXXXX
> 
thanx for your reply, i will give it a try, but this kind of init
needs some more rewrite i have expected and i have currently no
iec958-capable-device to do real tests, so users have to wait bit ;)

> well, it seems that ens1371 has still no configuration for iec958.
> so, the right way is to add this stuff...
?
should i add it? will you add it? on which device is the iec958
running on the ens1371? i guess its hw:0,0

-- 
regards

____-
joy

________/\---------%%%___________-----------
webcast every sunday 2000 cest at pingfm.org

pgp key at: x-hkp://wwwkeys.de.pgp.net


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

  reply	other threads:[~2002-07-17 22:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-13 15:19 spdif-trough and snd_ctl_elem_* joy
2002-07-17 12:25 ` Takashi Iwai
2002-07-17 22:31   ` joy [this message]
2002-07-19 18:03     ` Takashi Iwai
2002-07-20  7:11       ` Jaroslav Kysela

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=20020717223116.GA3310@pingfm.org \
    --to=joy@pingfm.org \
    --cc=alsa-devel@lists.sourceforge.net \
    /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