From: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>
To: "Stas Sergeev" <stsp@aknet.ru>
Cc: "Linux kernel" <linux-kernel@vger.kernel.org>, vojtech@suse.cz
Subject: Re: [patch 1/1] pc-speaker: add SND_SILENT
Date: Thu, 23 Mar 2006 13:47:46 -0500 [thread overview]
Message-ID: <d120d5000603231047q6e777243nb4031b701dbdc494@mail.gmail.com> (raw)
In-Reply-To: <4422E968.1050506@aknet.ru>
On 3/23/06, Stas Sergeev <stsp@aknet.ru> wrote:
> Hi.
>
> Dmitry Torokhov wrote:
> > OK, you need to tell me again what snd_pcsp and what exactly it
> > functions are, because I am confised at the moment.
> It is a PCM emulation driver - like any other ALSA PCM driver
> it can play a digital sound, emulating the 5bit PCM stream
> on a 1bit PC-Speaker device. (actually it pretends to be a
> 16bit stereo device, but what it produces is a 5bit mono sound)
>
> > If it is just for
> > playing sounds/music through PC speaker then I don't understand why
> > you want to disable pcspkr driver - if people don't like terminal
> > beeps they can disable it.
> The problem is that when the snd_pcsp is playing, the terminal beeps
> will "destroy" it, as they reprogram the PIT channel 2. So I need a
> way to disable pcspkr while the PCM is playing, but re-enable it as
> soon as the PCM output stopped.
So what you actually need is a mediator module controlling concurrent
access to the speaker hardware from both pcspkr and snd_pcsp and
making sure that one does not disrupt the other. This is completely
outside of the scope of the input subsystem tough.
> This only means people won't hear the terminal beeps while they "listen
> to the music", but this is not as big problem as disabling these beeps
> completely when snd_pcsp is selected in the config.
You are right, I misunderstood the purpose of snd_pcsp. Still the best
solution would be to allow beeps to come through if user keeps them
enabled.
--
Dmitry
next prev parent reply other threads:[~2006-03-23 18:47 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
2006-03-23 19:34 ` Stas Sergeev
2006-03-23 20:36 ` Dmitry Torokhov
2006-03-24 4:59 ` Stas Sergeev
[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 ` Bodo Eggert
2006-03-26 9:52 ` Stas Sergeev
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
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=d120d5000603231047q6e777243nb4031b701dbdc494@mail.gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=stsp@aknet.ru \
--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
all inboxes | Powered by JetHome®