From: Werner Almesberger <wa@almesberger.net>
To: "Martin J. Bligh" <mbligh@aracnet.com>
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 19:55:50 -0300 [thread overview]
Message-ID: <20030423195550.E3557@almesberger.net> (raw)
In-Reply-To: <1570840000.1051136330@flay>; from mbligh@aracnet.com on Wed, Apr 23, 2003 at 03:18:50PM -0700
Martin J. Bligh wrote:
> So if people want 0 volume for some reason, they can set *that*
> in userspace.
1) the kernel default is applied before, possibly long before user
space can provide its own value
2) the kernel itself doesn't use audio for any intentional interaction
with the user when booting
3) there can be unintentional audio output, e.g. from a source that
also has a non-zero default setting, or that starts in a random
state
4) you'll run a user space utility to adjust the volume, probably
before the user even gets a chance to do anything that would
cause intentional audio output
So, because of 4), your user space utility better gets it right, no
matter what the kernel does. If it screws up, your user loses.
3) may yield unexpected noise. Given that the expected behaviour
is silence (see 2), any sound at that point would be unexpected.
Because of 1), the kernel default should be such that a value
should be picked that has the least potential of causing unpleasant
surprises before user space takes over.
I don't quite see your point anyway. Because of 2), the only
situations in which a non-zero default would do anything useful
would be
- if you add audio output when booting a regular kernel
- if the user-space utility is absent, doesn't work properly, or
fails completely (if it fails, there'll probably be larger
obstacles than just adjusting the volume). Since for many
users, installing a new kernel equals upgrading their
distribution, fixes to any design errors in that user-space
part shouldn't be harder to deploy than a kernel-side change.
So are you planning to make the kernel sing a little song for us,
while booting ? :-)
(Now, for some constructive criticism: a user-space utility that
checks if there is on-going audio output with the volume set very
low, and pops up a wizard in such a case, might actually be
helpful. Likewise, audio output without an application accessing
the mixer may warrant a wizard.)
- Werner
--
_________________________________________________________________________
/ Werner Almesberger, Buenos Aires, Argentina wa@almesberger.net /
/_http://www.almesberger.net/____________________________________________/
next prev parent reply other threads:[~2003-04-23 22:44 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 [this message]
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
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
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=20030423195550.E3557@almesberger.net \
--to=wa@almesberger.net \
--cc=gigerstyle@gmx.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--cc=ms@citd.de \
--cc=pat@suwalski.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).