From: Takashi Iwai <tiwai@suse.de>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Stas Sergeev <stsp@aknet.ru>,
Roberto Oppedisano <roberto.oppedisano@infracom.it>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Non-working snd-pcsp
Date: Fri, 16 May 2008 17:23:24 +0200 [thread overview]
Message-ID: <s5h3aoie0ib.wl%tiwai@suse.de> (raw)
In-Reply-To: <alpine.LNX.1.10.0805161715470.15590@fbirervta.pbzchgretzou.qr>
At Fri, 16 May 2008 17:18:36 +0200 (CEST),
Jan Engelhardt wrote:
>
>
> On Friday 2008-05-16 15:40, Takashi Iwai wrote:
> >>
> >> If it does not even beep when issuing Ctrl-G on the shell,
> >> you probably need to modprobe pcspkr, if it is not built-in.
> >> (At least this is with kernels a little less
> >> recent than 2.6.25. )
> >
> >If snd-pcsp module is built, input pcspkr module won't be built...
>
> 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.
>
> Now, if pcspkr is deactivated when snd-pcsp is built... I would
> not get any tone out of that piece of hardware.
> Except if snd-pcsp itself contains beep code, and that would
> be sort of redundant when it is already in pcspkr.
Indeed snd-pcsp contains the input pcspkr code. Yes, it's redundant,
but separating them isn't trivial.
Takashi
next prev parent reply other threads:[~2008-05-16 15:23 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 [this message]
2008-05-16 15:24 ` Rene Herman
2008-05-19 18:10 ` Stas Sergeev
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=s5h3aoie0ib.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=jengelh@medozas.de \
--cc=linux-kernel@vger.kernel.org \
--cc=roberto.oppedisano@infracom.it \
--cc=stsp@aknet.ru \
/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).