From: Paul Vojta <vojta@Math.Berkeley.EDU>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: another device for opl3sa2
Date: Sun, 8 Jul 2007 01:02:24 -0700 [thread overview]
Message-ID: <20070708080224.GA14178@math.berkeley.edu> (raw)
In-Reply-To: <s5hy7ht50ir.wl%tiwai@suse.de>
On Fri, Jul 06, 2007 at 11:45:00AM +0200, Takashi Iwai wrote:
> 0x0b = CS4231_TEST_INIT, and 0x20 = CS4231_CALIB_IN_PROGRESS.
> At least, mce_down() should show messages if the calibration gets
> timeout. Did you see any related messages? Or didn't you build with
> --with-debug=full?
I didn't build with --debug=full. I've been using ALSA as supplied with
linux kernel 2.6.21.1, and built without CONFIG_SND_DEBUG or
CONFIG_SND_DEBUG_DETECT
I have now switched to 2.6.21.6, and turned on both of CONFIG_SND_DEBUG*.
I also uncommented the printk() calls in mce_down(), and moved the first
one down below the definition of the variable 'timeout'.
Here are the kernel messages I got:
Device opl3sa2:
Initialization
ALSA sound/isa/cs423x/cs4231_lib.c:1015: cs4231: port = 0x534, id = 0xa
(1) timeout = 12
(1) timeout = 95
(1) timeout = 31
(1) timeout = 73
(1) timeout = 80
(1) timeout = 72
(1) timeout = 92
Ran aplay first time (no sound)
ALSA sound/isa/cs423x/cs4231_lib.c:331: mce_down [0x0] - auto calibration time out (0)
(1) timeout = 72
Ran aplay second time
(1) timeout = 72
Device cs4232:
Initialization
ALSA sound/isa/cs423x/cs4231_lib.c:1015: cs4231: port = 0x534, id = 0xa
ALSA sound/isa/cs423x/cs4231_lib.c:1021: CS4231: VERSION (I25) = 0x80
(1) timeout = 23
(1) timeout = 95
(1) timeout = 11
(1) timeout = 73
(1) timeout = 80
(1) timeout = 72
(2) timeout = 495, jiffies = -64562
(3) jiffies = -64558
(4) jiffies = -64558
ALSA sound/isa/cs423x/cs4231_lib.c:383: mce_down - exit = 0xb
(1) timeout = 92
Ran aplay first time
ALSA sound/isa/cs423x/cs4231_lib.c:331: mce_down [0x0] - auto calibration time out (0)
(1) timeout = 72
(2) timeout = 500, jiffies = -45004
(3) jiffies = -45000
(4) jiffies = -45000
ALSA sound/isa/cs423x/cs4231_lib.c:383: mce_down - exit = 0xb
Ran aplay second time
(1) timeout = 72
--Paul Vojta, vojta@math.berkeley.edu
next prev parent reply other threads:[~2007-07-08 8:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-03 0:27 another device for opl3sa2 Paul Vojta
2007-07-03 10:05 ` Takashi Iwai
2007-07-04 2:24 ` Paul Vojta
2007-07-04 8:53 ` Takashi Iwai
2007-07-05 8:03 ` Paul Vojta
2007-07-05 14:38 ` Takashi Iwai
2007-07-06 7:41 ` Paul Vojta
2007-07-06 9:45 ` Takashi Iwai
2007-07-08 8:02 ` Paul Vojta [this message]
2007-07-09 12:42 ` Takashi Iwai
2007-07-09 18:14 ` Paul Vojta
2007-07-27 7:55 ` Paul Vojta
2007-07-27 10:22 ` 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=20070708080224.GA14178@math.berkeley.edu \
--to=vojta@math.berkeley.edu \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.de \
/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