From: Stephen Thomas <stephen.thomas@insignia.com>
To: Mark Hindley <mh15@st-andrews.ac.uk>
Cc: linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: opl3 under 2.4.0-test10
Date: Sat, 11 Nov 2000 20:34:24 +0000 [thread overview]
Message-ID: <3A0DAD50.8C55A494@insignia.com> (raw)
In-Reply-To: <200011110826.IAA01091@hindleyhome.st-andrews.ac.uk>
Mark Hindley wrote:
> I am trying to setup my ALS 110 soundcard under my build of kernel
> 2.4.0-test10.
>
> I have built in isapnp support and also the sb and opl3 drivers.
>
> However, even though I pass opl3=0x388 on the Kernel command line all
> I get is an isapnp panic.
I'm experiencing what superficially appears to be a related problem
with an AWE64 card. I'm building the drivers non-modular (because
I've yet to find any description of how to configure modular sound
drivers for 2.4.0). I believe I'm making the appropriate configuration
settings - from my .config:
CONFIG_SOUND=y
CONFIG_SOUND_OSS=y
CONFIG_SOUND_TRACEINIT=y
CONFIG_SOUND_DMAP=y
CONFIG_SOUND_ADLIB=y
CONFIG_SOUND_VMIDI=y
CONFIG_SOUND_SB=y
CONFIG_SOUND_AWE32_SYNTH=y
CONFIG_SOUND_YM3812=y
and I'm passing "opl3=0x388" to the driver. However, if I query
what synth devices the driver supports, it only reports an
AWE32-0.4.4 (RAM512k) sample device. I expect it report an FM synth
device, too. I get the same (lack of) effect if I go via the
adlib_card code, by saying "adlib=0x388". My investigations so
far have shown that when opl3_detect() first tries to get the
signature of the OPL3 device, it gets 0xff from the inb() (line
195 of drivers/sound/opl3.c in test11pre1), while the corresponding
code in 2.2.18pre19 gets 0x00.
Stephen Thomas
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-11 20:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-11 8:26 opl3 under 2.4.0-test10 Mark Hindley
2000-11-11 20:34 ` Stephen Thomas [this message]
2000-11-11 21:55 ` Thomas Molina
2000-11-13 11:51 ` Mark Hindley
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=3A0DAD50.8C55A494@insignia.com \
--to=stephen.thomas@insignia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=mh15@st-andrews.ac.uk \
/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