From: David Bronaugh <dbronaugh@opensourcedot.com>
To: linux-kernel@vger.kernel.org
Subject: Breakage of opl3sax cards since 2.4.3 (at least)
Date: Tue, 1 May 2001 15:39:41 -0700 [thread overview]
Message-ID: <20010501153941.E498@Woodbox.gv.shawcable.net> (raw)
OK, cutting to chase:
opl3sax cards have refused to init in Linux with the in-kernel OSS driver
since 2.4.3 at least (last I tested and worked was 2.4.1). I'm pretty sure
this is a kernel issue as it's happened on 2 different machines, one of
which I never goofed around with.
Usually message is something like:
opl3sa2: Control I/O port 0x220 (or whatever is tried) is not a YMF7xx
chipset!
I'm not sure why this occurs, but here is the code block where the error
probably occurs:
/* SNIP */
opl3sa2_read(hw_config->io_base, OPL3SA2_MISC, &misc);
opl3sa2_write(hw_config->io_base, OPL3SA2_MISC, misc ^ 0x07);
opl3sa2_read(hw_config->io_base, OPL3SA2_MISC, &tmp);
if(tmp != misc) {
printk(KERN_ERR "opl3sa2: Control I/O port %#x is not a
YMF7xx chipset!\n",
hw_config->io_base);
return 0;
}
/*
* Check if the MIC register is accessible.
*/
opl3sa2_read(hw_config->io_base, OPL3SA2_MIC, &tmp);
opl3sa2_write(hw_config->io_base, OPL3SA2_MIC, 0x8a);
opl3sa2_read(hw_config->io_base, OPL3SA2_MIC, &tmp);
if((tmp & 0x9f) != 0x8a) {
printk(KERN_ERR
"opl3sa2: Control I/O port %#x is not a YMF7xx
chipset!\n",
hw_config->io_base);
return 0;
}
/* SNIP */
Maybe this is a dumb check because there's an anomaly with the OPL3SAx
chip. I don't know.
I'm not on the list, so please forward any mail sent about this to me.
David Bronaugh
next reply other threads:[~2001-05-01 22:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-01 22:39 David Bronaugh [this message]
2001-05-01 23:26 ` Vivek Dasmohapatra
2001-05-02 7:09 Russ Dill
2001-05-02 8:30 ` Vivek Dasmohapatra
2001-05-02 8:50 ` Russ Dill
2001-05-02 8:55 ` Vivek Dasmohapatra
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=20010501153941.E498@Woodbox.gv.shawcable.net \
--to=dbronaugh@opensourcedot.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®