From: Takashi Iwai <tiwai@suse.de>
To: Santiago Garcia Mantinan <manty@manty.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ALSA in 2.6 failing to find the OPL chip of the sb cards
Date: Fri, 09 Jan 2004 18:37:45 +0100 [thread overview]
Message-ID: <s5hn08xgh06.wl@alsa2.suse.de> (raw)
In-Reply-To: <20040109171715.GA933@man.manty.net>
At Fri, 9 Jan 2004 18:17:15 +0100,
Santiago Garcia Mantinan wrote:
>
> > compile with CONFIG_SND_DEBUG and CONFIG_SND_VERBOSE_PRINTK.
> > if it's in snd_opl3_detect(), "OPL2/3 chip not detected at ..."
> > message should appear (together with other message in
> > snd_opl3_detect()).
>
> I have tested now with 2.6.1 with vanilla driver (0.9.7) and also with 1.0.1
> using the patch that Jaroslav posted yesterday available at
> ftp://ftp.alsa-project.org/pub/kernel-patches/alsa-bk-2004-01-08.patch.gz
> and got the same result as before, these are the messages for 1.0.1:
>
> pnp: Device 00:01.00 activated.
> ALSA sound/isa/sb/sb16.c:313: pnp SB16: port=0x220, mpu port=0x330, fm port=0x388
> ALSA sound/isa/sb/sb16.c:315: pnp SB16: dma1=1, dma2=5, irq=10
> ALSA sound/isa/sb/sb_common.c:133: SB [0x220]: DSP chip found, version = 4.13
> ALSA sound/drivers/opl3/opl3_lib.c:133: OPL3: stat1 = 0xff
> ALSA sound/drivers/opl3/opl3_lib.c:444: OPL2/3 chip not detected at 0x388/0x38a
> ALSA sound/isa/sb/sb16.c:489: sb16: no OPL device at 0x388-0x38a
then it fails in the reset sequence of opl chip, namely,
what happens if you replace the line 441
opl3->command = &snd_opl2_command;
with
opl3->command = &snd_opl3_command;
?
--
Takashi Iwai <tiwai@suse.de> ALSA Developer - www.alsa-project.org
next prev parent reply other threads:[~2004-01-09 17:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 21:29 ALSA in 2.6 failing to find the OPL chip of the sb cards Santiago Garcia Mantinan
2004-01-08 17:21 ` Takashi Iwai
2004-01-08 22:42 ` Santiago Garcia Mantinan
2004-01-09 17:17 ` Santiago Garcia Mantinan
2004-01-09 17:37 ` Takashi Iwai [this message]
2004-01-09 20:14 ` Santiago Garcia Mantinan
2004-01-10 7:24 ` Rene Herman
2004-01-11 5:33 ` [PATCH] " Rene Herman
2004-01-12 15:35 ` Takashi Iwai
2004-01-13 23:29 ` Adam Belay
2004-01-14 19:07 ` Adam Belay
2004-01-15 0:36 ` Rene Herman
2004-01-15 23:35 ` Rene Herman
2004-01-18 22:26 ` Santiago Garcia Mantinan
2004-01-12 21:14 ` Santiago Garcia Mantinan
2004-01-12 15:31 ` Takashi Iwai
2004-01-12 20:51 ` Rene Herman
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=s5hn08xgh06.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=manty@manty.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 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.