From: John Rigg <j@sound-man.co.uk>
To: Doug McLain <doug@nostar.net>
Cc: alsa-devel@lists.sourceforge.net, jackit-devel@lists.sourceforge.net
Subject: Re: [Alsa-devel] Re: Real-world reports on two Delta 1010LTs/ice1712 synched?
Date: Tue, 27 Dec 2005 13:00:29 +0000 [thread overview]
Message-ID: <20051227130029.GB3770@localhost.localdomain> (raw)
In-Reply-To: <43B0A83F.1040907@nostar.net>
On Mon, Dec 26, 2005 at 09:34:39PM -0500, Doug McLain wrote:
> All of the envy24control code treats the 1010 and 1010LT equally, so if
> there is a difference, its in the hardware of the devices:
>
> if (card_eeprom.subvendor == ICE1712_SUBDEVICE_DELTA1010 ||
> card_eeprom.subvendor == ICE1712_SUBDEVICE_DELTA1010LT) {
> delta specific stuff here...
>
> I find it strange that the envy24control patch does not change anything
> for me. What exactly was your issue with envy24control before applying
> that patch?
With 2.6.14 or later kernel, starting envy24control (from alsa-tools-1.0.10)
from xterm resulted in a slew of error messages saying "Unable to determine
word clock status" scrolling off the xterm. The patch fixed that. Maybe that
only happens with the 1010 not the 1010LT. It's possible that with the broken
word clock on the 1010LT it wasn't even trying to determine word clock
status so it didn't trigger the bug.
John
-------------------------------------------------------
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:[~2005-12-27 13:00 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 ` John Rigg [this message]
2005-12-27 20:50 ` 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 ` Re: [Jackit-devel] " Lee Revell
2006-01-18 10:56 ` 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=20051227130029.GB3770@localhost.localdomain \
--to=j@sound-man.co.uk \
--cc=alsa-devel@lists.sourceforge.net \
--cc=doug@nostar.net \
--cc=jackit-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