From: "Riley Williams" <Riley@Williams.Name>
To: "James Simmons" <jsimmons@infradead.org>, <junkio@cox.net>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: "Where's the Beep?" (PCMCIA/vt_ioctl-s)
Date: Thu, 17 Jul 2003 22:09:15 +0100 [thread overview]
Message-ID: <BKEGKPICNAKILKJKMHCAIEMGEOAA.Riley@Williams.Name> (raw)
In-Reply-To: <Pine.LNX.4.44.0307151750090.7746-100000@phoenix.infradead.org>
Hi James.
>>>> On my old DELL LM laptop the -2.5 series no longer issues
>>>> any beeps when a card is inserted. The problem is in the
>>>> kernel, as the test program below (extracted from cardmgr)
>>>> beeps on -2.4, but not on -2.5.
>>> CONFIG_INPUT_PCSPKR needs to be =y (or =m and the module
>>> loaded).
>> That's true, but I wonder why PC Speaker is under *INPUT*
>> category...
> Because many keyboards have built in speakers.
What sort of logic is that !!!
The ONLY reason I can think of for treating a speaker as an INPUT
device is if that speaker is wired up in a way that allows it to
be used as a microphone, the way some baby-intercoms do. If this
is the reason, then don't expect any sort of quality from it, and
please also separate this use from the more conventional one.
Best wishes from Riley.
---
* Nothing as pretty as a smile, nothing as ugly as a frown.
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.501 / Virus Database: 299 - Release Date: 14-Jul-2003
next prev parent reply other threads:[~2003-07-17 20:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.hjqfgl8.17m6f00@ifi.uio.no>
[not found] ` <fa.h26ngau.73iiag@ifi.uio.no>
2003-07-15 10:22 ` "Where's the Beep?" (PCMCIA/vt_ioctl-s) junkio
2003-07-15 16:50 ` James Simmons
2003-07-17 21:09 ` Riley Williams [this message]
2003-07-20 23:48 ` Neil Brown
2003-07-15 7:48 B. D. Elliott
2003-07-15 7:53 ` Neil Brown
2003-07-15 14:29 ` Valdis.Kletnieks
2003-07-15 19:03 ` Valdis.Kletnieks
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=BKEGKPICNAKILKJKMHCAIEMGEOAA.Riley@Williams.Name \
--to=riley@williams.name \
--cc=jsimmons@infradead.org \
--cc=junkio@cox.net \
--cc=linux-kernel@vger.kernel.org \
/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).