From: Daniel Ritz <daniel.ritz@gmx.ch>
To: Zwane Mwaikambo <zwane@linuxpower.ca>
Cc: Adam Belay <ambx1@neo.rr.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2.5] OSS opl3sa2: bring in sync with 2.4
Date: Thu, 3 Apr 2003 02:04:44 +0200 [thread overview]
Message-ID: <200304030204.44258.daniel.ritz@gmx.ch> (raw)
In-Reply-To: <Pine.LNX.4.50.0304021751490.26002-100000@montezuma.mastecende.com>
On Thursday 03 April 2003 00:53, Zwane Mwaikambo wrote:
> On Sat, 29 Mar 2003, Daniel Ritz wrote:
> > hi adam
> >
> > for your oss-2.5 tree. this patch brings sound/oss/opl3sa2.c in sync with
> > 2.4. compiles and works (testes on my toshiba tecra 8000). against
> > 2.5.66-bk
>
> Firstly thank you very much for getting this done. Do you happen to use
> isapnp for configuration?
yes, a plain "modprobe opl3sa2" is enough, no params, nothing in modprobe.conf...
(and it's actually playing sound)
>
> Thanks,
> Zwane
rgds
-daniel
prev parent reply other threads:[~2003-04-02 23:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-29 19:40 [PATCH 2.5] OSS opl3sa2: bring in sync with 2.4 Daniel Ritz
2003-04-02 15:52 ` Adam Belay
2003-04-02 22:53 ` Zwane Mwaikambo
2003-04-03 0:04 ` Daniel Ritz [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=200304030204.44258.daniel.ritz@gmx.ch \
--to=daniel.ritz@gmx.ch \
--cc=ambx1@neo.rr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@linuxpower.ca \
/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