lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1155161498.26338.216.camel@mindpipe>
Date:	Wed, 09 Aug 2006 18:11:37 -0400
From:	Lee Revell <rlrevell@...-job.com>
To:	Alistair John Strachan <s0348365@....ed.ac.uk>
Cc:	Gene Heskett <gene.heskett@...izon.net>,
	linux-kernel@...r.kernel.org, Andrew Benton <b3nt@...nline.co.uk>,
	Takashi Iwai <tiwai@...e.de>,
	alsa-devel <alsa-devel@...ts.sourceforge.net>
Subject: Re: ALSA problems with 2.6.18-rc3

On Wed, 2006-08-09 at 23:07 +0100, Alistair John Strachan wrote:
> > It's impossible to predict the effect of some mixer controls across
> the
> > wide range of hardware that ALSA supports.  What makes sound work on
> one
> > machine is likely to break it on another.
> 
> However, ALSA _has_ defaults for these controls, which I believe are 
> usually "off" or "zero". All I'm suggesting is that these defaults are
> plainly suboptimal for emu10k1, and probably other cards to which this
> statement simply does not apply. Shipping defaults is one thing, but
> shipping useless defaults is quite another. We have policy all over
> the kernel for providing "sane defaults" e.g. filesystem mount
> options. 

I think muted is a sane default - the only sane default.  Otherwise you
could damage speakers or hearing.  Also many devices will be noisier if
unused inputs are enabled.  Is it really that hard for users to unmute
the mixer or for distros to create their own config?

Also, analog output on my emu10k1 works perfectly with "External
Amplifier" disabled.

Lee

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ