From: Doug McLain <doug@nostar.net>
To: Alan Horstmann <gineera@aspect135.co.uk>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: ice1712 -wordclock and SPDIF
Date: Fri, 03 Feb 2006 11:24:26 -0500 [thread overview]
Message-ID: <43E383BA.1040204@nostar.net> (raw)
In-Reply-To: <200602020947.29156.gineera@aspect135.co.uk>
Alan Horstmann wrote:
> On Wednesday 01 February 2006 21:30, you wrote:
>
>>CS8427 register dump:
>> reg[0x01] = 0x81
>> reg[0x02] = 0x00
>> reg[0x03] = 0x0c
>> reg[0x04] = 0x41
>
>
> I have been looking at reg0x04 for bug1785; value 41 means the AES3 bit
> (bit'0') is set, which will mess-up SPDIF IN. Perhaps try the reset patch on
> that report. With DMX6fire it is often re-written correctly anyway, so it
> may be a similar but separate problem here.
>
> However, reg0x03 I notice now also looks wrong, and controls the output data
> source with bits'1'&'2': value 0c means bits are '1,0' =sourced from AES3
> receiver. Think it should be '0,1' ie reg value 0a?
setting it to 0x0a breaks it completely, as in no spdif functionality no
way, no how. Patches didnt help either. Wtih any luck, the status of
your registers may tell the story.
>
> Busy few evenings, but will get full info dump fromDMX6fire asap.
>
Thanks
Doug
--
http://nostar.net
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
prev parent reply other threads:[~2006-02-03 16:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-26 23:01 ice1712 -wordclock and SPDIF Alan Horstmann
[not found] ` <43DA6EB0.3030203@nostar.net>
[not found] ` <200601281424.14897.gineera@aspect135.co.uk>
2006-02-01 21:30 ` Doug McLain
2006-02-02 9:47 ` Alan Horstmann
2006-02-03 16:24 ` Doug McLain [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=43E383BA.1040204@nostar.net \
--to=doug@nostar.net \
--cc=alsa-devel@lists.sourceforge.net \
--cc=gineera@aspect135.co.uk \
/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