linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stas Sergeev <stsp@aknet.ru>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Takashi Iwai <tiwai@suse.de>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Non-working snd-pcsp
Date: Mon, 19 May 2008 22:10:11 +0400	[thread overview]
Message-ID: <4831C283.3050306@aknet.ru> (raw)
In-Reply-To: <alpine.LNX.1.10.0805161715470.15590@fbirervta.pbzchgretzou.qr>

Hello.

Jan Engelhardt wrote:
> Previously, with Stas's standalone patch, one was able to switch
> between (a) no speaker (b) beep/pcspkr (c) beep/pcspkr and
> PCM/snd-pcsp, all by means of modprobe/rmmod.
But now you can get any such combination
by the use of alsamixer only.

> Except if snd-pcsp itself contains beep code, and that would
> be sort of redundant when it is already in pcspkr.
It is redundant only if you _intend_
to use both drivers. But its usually
a bad idea to have multiple drivers
serving the single device simultaneously.
The other way of thinking about it,
is that you simply use a new driver
instead of an old one. The new one
does everything the old one did and
more. Since they can't be built together,
the redundancy is then only in a source
code.
I am not saying it is an ideal solution.
It is not, but for only a single reason -
people who need only beeps, may not
want to have the entire sound subsystem
loaded. So they want pcspkr to be at
least built. But getting these drivers
back together again, suddenly became
very problematic...

  parent reply	other threads:[~2008-05-19 18:10 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-11 18:15 2.6.26-rc1 regression: e5e1d3cb20034a3cbcfff1f0bae12201aa2ce17e breaks artsd Roberto Oppedisano
2008-05-11 18:56 ` Stas Sergeev
2008-05-11 20:28   ` Roberto Oppedisano
2008-05-11 20:56     ` Stas Sergeev
2008-05-12  7:24       ` Roberto Oppedisano
2008-05-12 18:22         ` Stas Sergeev
2008-05-13 14:00           ` Roberto Oppedisano
2008-05-13 15:41             ` Roberto Oppedisano
2008-05-13 16:50               ` Non-working snd-pcsp Takashi Iwai
2008-05-14  5:35                 ` Roberto Oppedisano
2008-05-14 10:03                   ` Takashi Iwai
2008-05-15 20:17                     ` Roberto Oppedisano
2008-05-15 20:38                       ` Stas Sergeev
2008-05-16 13:15                         ` Jan Engelhardt
2008-05-16 13:40                           ` Takashi Iwai
2008-05-16 15:18                             ` Jan Engelhardt
2008-05-16 15:23                               ` Takashi Iwai
2008-05-16 15:24                               ` Rene Herman
2008-05-19 18:10                               ` Stas Sergeev [this message]
2008-05-17 12:02                         ` Non-working snd-pcsp - solved Roberto Oppedisano
2008-05-17 15:50                           ` [patch] snd-pcsp: silent misleading warning Stas Sergeev
2008-05-18  7:44                             ` Takashi Iwai
2008-05-18 17:32                               ` Stas Sergeev
2008-05-18 16:28                                 ` Takashi Iwai
2008-05-18 16:49                                   ` Stas Sergeev
2008-05-14 19:59               ` Non-working snd-pcsp Stas Sergeev

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=4831C283.3050306@aknet.ru \
    --to=stsp@aknet.ru \
    --cc=jengelh@medozas.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tiwai@suse.de \
    /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).