From: Stas Sergeev <stsp@aknet.ru>
To: 7eggert@gmx.de
Cc: dtor_core@ameritech.net,
Linux kernel <linux-kernel@vger.kernel.org>,
vojtech@suse.cz
Subject: Re: [patch 1/1] pc-speaker: add SND_SILENT
Date: Sun, 26 Mar 2006 13:52:50 +0400 [thread overview]
Message-ID: <44266472.5080309@aknet.ru> (raw)
In-Reply-To: <E1FMv1A-0000fN-Lp@be1.lrz>
Hello.
Bodo Eggert wrote:
>> The problem is that the snd-pcsp doesn't replace pcspkr.
> If that's the problem, create a minimal input driver that will signal the
> snd-pcsp to beep, and change the original pcspkr to include "(Non-ALSA)".
Yes, making snd-pcsp to produce the console beeps and
making it mutually exclusive with pcspkr is possible.
But I think it is undesireable. People that don't like
the console beeps (myself included) simply do not load
the pcspkr module right now. If snd-pcsp is to produce
the beeps, then not loading pcspkr will not get the desired
effect any more, and the only possibility would be to,
probably, add the separate mixer control for the beeps.
I find this counter-intuitive: some people will be able to
disable the beeps by simply not loading pcspkr, while for
others this will suddenly magically stop working. This may
lead to a few unnecessary bug reports and confusions.
I think I'd better try to code up the grabbing capability in
the input layer, since Dmitry didn't seem to object to that.
next prev parent reply other threads:[~2006-03-26 10:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5TCqf-E6-49@gated-at.bofh.it>
[not found] ` <5TCqf-E6-51@gated-at.bofh.it>
[not found] ` <5TCqf-E6-53@gated-at.bofh.it>
[not found] ` <5TCqg-E6-55@gated-at.bofh.it>
[not found] ` <5TCqf-E6-47@gated-at.bofh.it>
2006-03-24 22:43 ` [patch 1/1] pc-speaker: add SND_SILENT Bodo Eggert
2006-03-26 9:52 ` Stas Sergeev [this message]
2006-03-26 11:24 ` Bodo Eggert
2006-03-26 18:46 ` Jan Engelhardt
2006-03-26 20:15 ` Kyle Moffett
2006-03-27 16:34 ` Dmitry Torokhov
2006-03-27 17:36 ` Stas Sergeev
2006-04-08 8:02 ` Stas Sergeev
2006-03-28 18:31 ` Joseph Fannin
2006-03-28 18:43 ` Bodo Eggert
2006-03-28 18:51 ` Vojtech Pavlik
2006-03-30 23:07 ` Edgar Toernig
2006-03-31 7:46 ` Vojtech Pavlik
2006-03-31 21:06 ` Edgar Toernig
2006-04-01 6:11 ` Vojtech Pavlik
[not found] <200603220652.k2M6qZgi020656@shell0.pdx.osdl.net>
[not found] ` <d120d5000603221332n6a6f9208x5651dc9ec993f4bf@mail.gmail.com>
[not found] ` <4422318C.407@aknet.ru>
[not found] ` <d120d5000603230651p6b43aad9ocad1aa3c2b51b388@mail.gmail.com>
2006-03-23 18:03 ` Stas Sergeev
2006-03-23 18:12 ` Dmitry Torokhov
2006-03-23 18:31 ` Stas Sergeev
2006-03-23 18:47 ` Dmitry Torokhov
2006-03-23 19:34 ` Stas Sergeev
2006-03-23 20:36 ` Dmitry Torokhov
2006-03-24 4:59 ` 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=44266472.5080309@aknet.ru \
--to=stsp@aknet.ru \
--cc=7eggert@gmx.de \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.cz \
/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