From: Simon Huggins <huggie@earth.li>
To: linux-sound@vger.kernel.org
Subject: Re: [PATCH] Ensoniq SoundScape with 2.3.51 (mpu401 changes broke it)
Date: Mon, 13 Mar 2000 17:18:33 +0000 [thread overview]
Message-ID: <marc-linux-sound-95305880326891@msgid-missing> (raw)
In-Reply-To: <marc-linux-sound-95287201901215@msgid-missing>
[-- Attachment #1: Type: text/plain, Size: 584 bytes --]
On Sun, Mar 12, 2000 at 06:54:22PM +0100, Christoph Hellwig wrote:
> > Can you decide whether you want to wrap this in some magical #ifdef's
> > and send it on to Linus?
> You can send it to Linus, the changes seem ok.
This is a better patch. It now unloads cleanly too.
Linus, please apply this to your tree. It fixes mpu401.c for the
Ensoniq SoundScape.
--
Simon [ huggie@earth.li ] *\ "Cockroaches! They're \**
****** ]-+-+-+-+-+-+-+-+-[ **\ everywhere...uuugghh...I'm \*
****** [ Htag.pl 0.0.4 ] ***\ surrounded!" - Mulder \
[-- Attachment #2: mpu401.diff --]
[-- Type: text/plain, Size: 801 bytes --]
--- mpu401.c.old Sun Mar 12 14:17:11 2000
+++ mpu401.c Mon Mar 13 17:13:13 2000
@@ -1726,25 +1726,24 @@
{
/* Can be loaded either for module use or to provide functions
to others */
- cfg.irq = irq;
- cfg.io_base = io;
-
- if (cfg.io_base != -1 && cfg.irq != -1) {
- printk(KERN_WARNING "mpu401: need io and irq !");
- return -ENODEV;
+ if (io != -1 && irq != -1) {
+ cfg.irq = irq;
+ cfg.io_base = io;
+ if (probe_mpu401(&cfg) == 0)
+ return -ENODEV;
+ attach_mpu401(&cfg);
}
- if (probe_mpu401(&cfg) == 0)
- return -ENODEV;
- attach_mpu401(&cfg);
-
SOUND_LOCK;
return 0;
}
void cleanup_mpu401(void)
{
- unload_mpu401(&cfg);
+ if (io != -1 && irq != -1) {
+ /* Check for use by, for example, sscape driver */
+ unload_mpu401(&cfg);
+ }
SOUND_LOCK_END;
}
prev parent reply other threads:[~2000-03-13 17:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-12 14:35 [PATCH] Ensoniq SoundScape with 2.3.51 (mpu401 changes broke it) Simon Huggins
2000-03-13 17:18 ` Simon Huggins [this message]
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=marc-linux-sound-95305880326891@msgid-missing \
--to=huggie@earth.li \
--cc=linux-sound@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 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.