From: "Alejandro Bonilla" <abonilla@linuxwireless.org>
To: "'Lee Revell'" <rlrevell@joe-job.com>
Cc: "'kernel list'" <linux-kernel@vger.kernel.org>
Subject: RE: ipw2100: firmware problem
Date: Fri, 10 Jun 2005 15:18:54 -0600 [thread overview]
Message-ID: <003201c56e02$025d0e10$600cc60a@amer.sykes.com> (raw)
In-Reply-To: <1118437639.6423.65.camel@mindpipe>
> > Riiiight. It could be. Or it could be that no where in the
> world I have seen
> > something where the device would be disabled by default
> without notifying
> > the user. Why would you Mute the driver? Is the driver that
> bad, that the
> > developers would rather Mute the sound card, just in case
> if the sound cards
> > starts making noises and shit when the driver is loaded?
> >
>
> Userspace should handle it, doing this in the kernel is bloat.
I Agreed to this since 8 AM.
>
> My Debian system initializes the mixer settings to a sane state just
> fine when the alsasound init script is run. Maybe you need a better
> distro.
I use Debian.
>
> Users who compile ALSA from source are expected to know what they are
> doing. And, if you watch the "make install" output, it
> prints a big fat
> warning that all mixer controls are muted by default.
Who said I did it from source?
>
> > You are moving to another topic. Let's drop it.
>
> Agreed, but it was your OT rant that changed the topic...
>
> Lee
dropped.
.Alejandro
next prev parent reply other threads:[~2005-06-10 21:19 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-08 14:23 Pavel Machek
2005-06-08 14:44 ` Denis Vlasenko
2005-06-08 14:56 ` Jirka Bohac
2005-06-08 15:24 ` Tomasz Torcz
2005-06-08 16:29 ` Pavel Machek
2005-06-21 7:42 ` Simon Kelley
2005-06-21 8:29 ` Feyd
2005-06-21 8:46 ` Simon Kelley
2005-06-08 15:05 ` Alejandro Bonilla
2005-06-08 15:23 ` Jiri Benc
2005-06-09 6:09 ` Denis Vlasenko
2005-06-09 6:16 ` David S. Miller
2005-06-09 6:25 ` Denis Vlasenko
2005-06-09 6:28 ` David S. Miller
2005-06-09 6:37 ` Denis Vlasenko
2005-06-09 8:36 ` Wichert Akkerman
2005-06-09 10:42 ` Pavel Machek
2005-06-09 19:53 ` David S. Miller
2005-06-09 21:01 ` James Ketrenos
2005-06-09 21:15 ` Arjan van de Ven
2005-06-09 22:11 ` David S. Miller
2005-06-10 2:13 ` Jeff Garzik
2005-06-10 2:46 ` Alejandro Bonilla
2005-06-10 9:00 ` Pavel Machek
2005-06-10 13:00 ` John Stoffel
2005-06-10 13:33 ` Alejandro Bonilla
2005-06-09 14:31 ` Alejandro Bonilla
2005-06-10 6:56 ` Denis Vlasenko
2005-06-10 13:23 ` Alejandro Bonilla
2005-06-10 20:26 ` Lee Revell
2005-06-10 21:00 ` Alejandro Bonilla
2005-06-10 21:07 ` Lee Revell
2005-06-10 21:18 ` Alejandro Bonilla [this message]
2005-06-13 16:42 ` Jan Rychter
2005-06-11 12:44 ` Denis Vlasenko
2005-06-08 17:10 ` James Ketrenos
2005-06-08 19:43 ` David S. Miller
2005-06-08 19:49 ` Dave Jones
2005-06-08 19:54 ` David S. Miller
2005-06-09 6:03 ` Denis Vlasenko
2005-06-09 6:10 ` David S. Miller
2005-06-09 6:17 ` Denis Vlasenko
2005-06-09 6:20 ` David S. Miller
2005-06-09 6:30 ` Denis Vlasenko
2005-06-09 6:35 ` David S. Miller
2005-06-10 3:51 ` Jim Crilly
2005-06-09 6:06 ` Jeff Garzik
2005-06-09 6:13 ` David S. Miller
2005-06-09 6:29 ` Jeff Garzik
2005-06-08 16:58 ` James Ketrenos
2005-06-08 21:27 ` Pavel Machek
2005-06-08 21:46 ` James Ketrenos
2005-06-08 22:34 ` Pavel Machek
2005-06-09 3:33 ` Zhu Yi
2005-06-09 10:56 ` Pavel Machek
2005-06-09 13:56 ` Andi Kleen
2005-06-09 21:12 ` Olivier Galibert
2005-06-09 23:13 ` Jeff Garzik
2005-06-11 17:06 ` Éric Brunet
2005-06-13 10:05 ` Zhu Yi
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='003201c56e02$025d0e10$600cc60a@amer.sykes.com' \
--to=abonilla@linuxwireless.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
/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
Powered by JetHome