From: Jerome AUGE <auge@irit.fr>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: opl3sa2 sound driver and mixers
Date: Tue, 30 Oct 2001 09:27:58 +0100 [thread overview]
Message-ID: <3BDE648E.135B39B8@irit.fr> (raw)
In-Reply-To: <Pine.LNX.4.33.0110300140020.20844-100000@rancor.yyz.somanetworks.com>
Scott Murray wrote:
>
> On Mon, 29 Oct 2001, Alan Cox wrote:
>
> > > Please read Documentation/sound/OPL3-SA2 (the two mixers are intentional,
> > > some channels are available only on the MSS mixer, others only on the
> > > OPL3-SA2), and don't break the driver! Since the latest DMA fix finally
> > > everything works fine on my Portege 3010 (which is exactly the same as the
> > > 3020 except for a slower CPU and smaller disk).
> >
> > Thanks for warning me and saving me the effort of decoding it all
>
> I've found myself too busy at work over the last while to really look into
> any issues with this driver. Anyone keen on taking over as maintainer?
>
Some times ago I wanted to change the mixer part and get back to the
"original" one, with a single mixer ... but as it was intentional, I
left it like this.
However I think it would be a good thing to present, to the user, a
single mixer. You have 1 or more soundcards and each soundcard have a
single mixer that control all the volume available with this card, no ?
If Alan has not yet released a patch that changes this ... I could try
to put all the controls back together ... and it will be the occasion to
learn a little bit more of that "mighty and scaring kernel" :)
--
next prev parent reply other threads:[~2001-10-30 8:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-29 19:39 opl3sa2 sound driver and mixers Alex Deucher
2001-10-29 19:56 ` Alan Cox
2001-10-29 20:08 ` Alex Deucher
2001-10-29 21:32 ` PALFFY Daniel
2001-10-29 21:40 ` Alan Cox
2001-10-30 6:48 ` Scott Murray
2001-10-30 8:27 ` Jerome AUGE [this message]
2001-10-30 15:38 ` Scott Murray
2001-10-29 20:21 ` Joel Becker
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=3BDE648E.135B39B8@irit.fr \
--to=auge@irit.fr \
--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 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.