From: Juri Haberland <juri.haberland@innominate.com>
To: rui.sousa@conexant.com
Cc: alan@lxorguk.ukuu.org.uk, emu10k1-devel@opensource.creative.com,
linux-kernel@vger.kernel.org, rsousa@grad.physics.sunysb.edu
Subject: Re: emu10k1 broken in 2.2.18
Date: Tue, 19 Dec 2000 10:03:25 +0100 [thread overview]
Message-ID: <3A3F245D.741EC27F@innominate.com> (raw)
In-Reply-To: <OF6B3623E3.C2E9E563-ONC12569BA.0030301F@conexant.com>
rui.sousa@conexant.com wrote:
>
> All reports I've seen mention that the driver works fine if compiled as a
> module. You may
> want to try that. For this reason I also don't believe the problem is the
> any of the emu10k1
> source files (which you diff'ed), unfortunately I haven't had much
> time/means to test this
> since I'm without a home PC and a SBLive.
Hi Rui,
this is unfortunately not true as I posted lately on emu10k1-devel.
If compiled as a module /dev/dsp and /dev/audio do _no_ work, but
/dev/dsp1 and /dev/audio1 do.
Someone posted a little patch that makes it work again. Here it is:
--- linux-2.2.18/drivers/sound/sound_core.c Sun Dec 17 11:11:46 2000
+++ linux-2.2.18-emubug/drivers/sound/sound_core.c Sun Dec 17
11:05:23 2000
@@ -436,7 +436,7 @@
cs4281_probe();
#endif
#ifdef CONFIG_SOUND_EMU10K1
- init_emu10k1();
+/* init_emu10k1();*/
#endif
#ifdef CONFIG_SOUND_YMFPCI
ymf_probe();
Greetings,
Juri
--
juri.haberland@innominate.com
system engineer innominate AG
clustering & security the linux architects
tel: +49-30-308806-45 fax: -77 http://www.innominate.com
-
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-12-19 9:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-19 8:51 emu10k1 broken in 2.2.18 rui.sousa
2000-12-19 9:03 ` Juri Haberland [this message]
2000-12-19 13:13 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2000-12-19 7:43 Ari Heitner
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=3A3F245D.741EC27F@innominate.com \
--to=juri.haberland@innominate.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=emu10k1-devel@opensource.creative.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rsousa@grad.physics.sunysb.edu \
--cc=rui.sousa@conexant.com \
/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.