From: Rene Herman <rene.herman@keyaccess.nl>
To: Andrew Paprocki <andrew@ishiboo.com>
Cc: ALSA development <alsa-devel@alsa-project.org>
Subject: Re: Proper way to set SCMS copy prohibited bits on IEC958 S/PDIF
Date: Thu, 31 Jul 2008 02:09:46 +0200 [thread overview]
Message-ID: <489102CA.4010809@keyaccess.nl> (raw)
In-Reply-To: <76366b180807301703n2dd1346dsa708ab60a7cc929f@mail.gmail.com>
On 31-07-08 02:03, Andrew Paprocki wrote:
> On Wed, Jul 30, 2008 at 8:01 PM, Rene Herman <rene.herman@keyaccess.nl> wrote:
>> On 30-07-08 22:37, Andrew Paprocki wrote:
>>
>>> I briefly checked the code for the Delta1010 (ice1712) to see if there
>>> was a way from user space to force the SCMS copy prohibited bits on in
>>> the S/PDIF stream. I see the driver initializes the bits to 0. Is
>>> there already a way to do this from user space, or would I have to
>>> modify the driver to force them on (or use a module parameter)?
>> I can't try this myself right now, but try "man iecset".
>
> I actually found this code as well: http://www.cs.tut.fi/~ik/mpegspdif/output.c
>
> It appears you can set the bits when opening the card by using a
> device string like this:
>
> sprintf(devstr, "iec958:AES0=0x%x,AES1=0x%x,AES2=0x%x,AES3=0x%x",
> s[0], s[1], s[2], s[3]);
>
> I'll look into both methods.
Yes, noticed that to (in /usr/share/alsa/pcm/iec958.conf) but couldn't
tell you what the %x were, so "iecset" seemed like better advice...
Rene.
next prev parent reply other threads:[~2008-07-31 0:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 20:37 Proper way to set SCMS copy prohibited bits on IEC958 S/PDIF Andrew Paprocki
2008-07-31 0:01 ` Rene Herman
2008-07-31 0:03 ` Andrew Paprocki
2008-07-31 0:09 ` Rene Herman [this message]
2008-07-31 9:59 ` Takashi Iwai
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=489102CA.4010809@keyaccess.nl \
--to=rene.herman@keyaccess.nl \
--cc=alsa-devel@alsa-project.org \
--cc=andrew@ishiboo.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.