From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Jamie Lokier <jamie@shareable.org>,
Werner Almesberger <wa@almesberger.net>
Cc: Matthias Schniedermeyer <ms@citd.de>,
Marc Giger <gigerstyle@gmx.ch>,
linux-kernel <linux-kernel@vger.kernel.org>,
pat@suwalski.net
Subject: Re: [Bug 623] New: Volume not remembered.
Date: Wed, 23 Apr 2003 18:18:46 -0700 [thread overview]
Message-ID: <1613630000.1051147126@flay> (raw)
In-Reply-To: <20030424011137.GA27195@mail.jlokier.co.uk>
>> I don't quite see how this would make user space any less
>> fancy:
>>
>> # insmod audio_driver volume=`retrieve_volume`
>>
>> versus
>>
>> # insmod audio_driver
>> # aumix -L >/dev/null
>
> Eh? I was suggesting that the _default_ just work as quite a few
> people expect:
>
> $ insmod audio_driver
>
> In fact, forget about "volume". Just have a "silent" parameter that
> defaults to 0, and determines whether the device starts silent or
> loads preset defaults. Make it a core audio thing rather than a
> per-driver thing, too. "silent=1" in /etc/modules.conf self-evidently
> answers the FAQ, too :)
Me like. Assuming this means what I think it does ;-)
The kernel sets a default quiet volume level (at first setup) to make some
sort of noise when used I first set up the machine so users don't get
confused ... save & restore volume levels on every boot from userspace.
If people want silent by default, they can change that in the
modules.conf / command line.
Is that what you meant?
M.
next prev parent reply other threads:[~2003-04-24 1:17 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-23 16:23 [Bug 623] New: Volume not remembered Martin J. Bligh
2003-04-23 16:32 ` Marc Giger
2003-04-23 16:45 ` Matthias Schniedermeyer
2003-04-23 16:56 ` Martin J. Bligh
2003-04-23 17:21 ` Matthias Schniedermeyer
2003-04-23 13:26 ` Pat Suwalski
2003-04-23 17:26 ` Martin J. Bligh
2003-04-23 17:45 ` Disconnect
2003-04-23 17:47 ` Matthias Schniedermeyer
2003-04-23 18:44 ` Martin J. Bligh
2003-04-23 17:49 ` Pat Suwalski
2003-04-23 18:56 ` Jörn Engel
2003-04-23 22:17 ` Pavel Machek
2003-04-23 22:35 ` Pat Suwalski
2003-04-23 22:55 ` Pavel Machek
2003-04-24 2:19 ` Werner Almesberger
2003-04-24 2:29 ` Pat Suwalski
2003-04-24 2:34 ` Ben Collins
2003-04-24 7:22 ` Jamie Lokier
2003-04-24 13:31 ` Werner Almesberger
2003-04-24 4:30 ` Valdis.Kletnieks
2003-04-23 23:15 ` Martin J. Bligh
2003-04-23 21:34 ` Werner Almesberger
2003-04-23 21:36 ` Martin J. Bligh
2003-04-23 22:14 ` Werner Almesberger
2003-04-23 22:18 ` Martin J. Bligh
2003-04-23 22:55 ` Werner Almesberger
2003-04-24 0:11 ` Jamie Lokier
2003-04-24 0:43 ` Werner Almesberger
2003-04-24 1:11 ` Jamie Lokier
2003-04-24 1:18 ` Martin J. Bligh [this message]
2003-04-24 1:22 ` Pat Suwalski
2003-04-24 2:11 ` Werner Almesberger
2003-04-24 2:40 ` Martin J. Bligh
2003-04-24 3:37 ` Werner Almesberger
2003-04-24 4:47 ` Martin J. Bligh
2003-04-24 13:16 ` Werner Almesberger
2003-04-24 7:14 ` Jamie Lokier
2003-04-24 13:38 ` Werner Almesberger
2003-04-24 13:49 ` Matthias Schniedermeyer
2003-04-24 14:08 ` Pat Suwalski
2003-04-24 14:34 ` Matthias Schniedermeyer
2003-04-24 15:04 ` Werner Almesberger
2003-04-24 15:23 ` Matthias Schniedermeyer
2003-04-24 16:01 ` Werner Almesberger
2003-04-24 16:26 ` Jaroslav Kysela
2003-04-24 21:22 ` Werner Almesberger
2003-04-25 10:03 ` Jaroslav Kysela
2003-04-25 10:30 ` Werner Almesberger
2003-04-24 21:36 ` Jamie Lokier
2003-04-24 23:55 ` Werner Almesberger
2003-04-25 0:05 ` Pat Suwalski
2003-04-25 10:41 ` Werner Almesberger
2003-04-25 10:04 ` Alan Cox
2003-04-25 17:44 ` Werner Almesberger
2003-04-25 17:59 ` Martin J. Bligh
2003-04-26 0:31 ` Pat Suwalski
2003-04-24 22:51 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2003-04-24 0:31 Ian Kumlien
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=1613630000.1051147126@flay \
--to=mbligh@aracnet.com \
--cc=gigerstyle@gmx.ch \
--cc=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ms@citd.de \
--cc=pat@suwalski.net \
--cc=wa@almesberger.net \
/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.