From: Lee Revell <rlrevell@joe-job.com>
To: Doug McLain <doug@nostar.net>
Cc: "Pasi Kärkkäinen" <pasik@iki.fi>, "John Rigg" <j@sound-man.co.uk>,
alsa-devel@lists.sourceforge.net,
jackit-devel@lists.sourceforge.net
Subject: Re: Re: [Jackit-devel] Real-world reports on two Delta 1010LTs/ice1712 synched?
Date: Mon, 16 Jan 2006 15:07:23 -0500 [thread overview]
Message-ID: <1137442044.19444.15.camel@mindpipe> (raw)
In-Reply-To: <43CBF383.3000807@nostar.net>
On Mon, 2006-01-16 at 14:26 -0500, Doug McLain wrote:
> I've been studying the ice1712 alsa driver closely over the past few
> weeks, and comparing all relevent ice1712 control register values in
> windows vs linux (in windows I got ahold of this nice program called
> PCIScope, a dream for reverse engineering pci hardware!) and I think
> (hope) the problem is in the init and configuration of the cs8427
> spdif transceiver. There are differences in bit values on the
> ice1712's GPIO data register. So my two areas of concern are
> deciphering the usage of the GPIO register and the cs8427 spdif
> transceiver. The ice1712 talks to the cs8427 over I2C, which isnt as
> straightforward to read as regular i/o registers, so it's more
> studying ahead. I am focusing on fixing spdif functionality, since
> the cs8427 datasheet is very clear about spdif operation. I am hoping
> by fixing regular spdif functionality on the ship, word clock will be
> fixed too. We'll see.
If you get stuck, SoftICE is also an incredibly useful tool for reverse
engineering Windows drivers.
Lee
-------------------------------------------------------
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://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
next prev parent reply other threads:[~2006-01-16 20:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20051223225430.GA4995@localhost.localdomain>
[not found] ` <43AC826C.1040405@nostar.net>
[not found] ` <20051223233816.GA5102@localhost.localdomain>
[not found] ` <43AC8990.7040900@nostar.net>
[not found] ` <20051224124823.GA4183@localhost.localdomain>
[not found] ` <20051224144548.GA4306@localhost.localdomain>
[not found] ` <20051224165610.GA4484@localhost.localdomain>
[not found] ` <43AE9FA6.2020207@nostar.net>
[not found] ` <20051226130327.GA4763@localhost.localdomain>
[not found] ` <43B059A3.2050302@nostar.net>
[not found] ` <20051227000428.GA3805@localhost.localdomain>
2005-12-27 2:34 ` [Jackit-devel] Real-world reports on two Delta 1010LTs/ice1712 synched? Doug McLain
2005-12-27 2:34 ` Doug McLain
[not found] ` <43B0A83F.1040907@nostar.net>
2005-12-27 5:06 ` Doug McLain
2005-12-27 5:06 ` Doug McLain
2005-12-27 13:00 ` [Alsa-devel] " John Rigg
2005-12-27 20:50 ` Re: [Jackit-devel] " Doug McLain
2005-12-28 21:19 ` John Rigg
2006-01-01 12:55 ` Doug McLain
2006-01-01 19:58 ` John Rigg
2006-01-16 17:56 ` [Alsa-devel] " Pasi Kärkkäinen
2006-01-16 19:26 ` Doug McLain
2006-01-16 20:07 ` Lee Revell [this message]
2006-01-18 10:56 ` Re: [Jackit-devel] " Alan Horstmann
2006-01-18 14:48 ` Alan Horstmann
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=1137442044.19444.15.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=doug@nostar.net \
--cc=j@sound-man.co.uk \
--cc=jackit-devel@lists.sourceforge.net \
--cc=pasik@iki.fi \
/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