LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: Linda Walsh <lkml@tlinx.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: x86-32-config: why is pc-speaker an input device?
Date: Fri, 15 Feb 2008 16:55:03 -0500	[thread overview]
Message-ID: <4387.1203112503@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Fri, 15 Feb 2008 13:19:11 PST." <47B601CF.9070300@tlinx.org>

[-- Attachment #1: Type: text/plain, Size: 1078 bytes --]

On Fri, 15 Feb 2008 13:19:11 PST, Linda Walsh said:
> I'm wondering how the generic, builtin PC-Speaker (config option
> "INPUT_PCSPKR") can be used as an input device.
> 
> If it can not be used for input, why is it under the input config section:
> 
> "Device Drivers"
> + -> "Input Device Support"
>      + -> "Miscellaneous devices"
>          + -> "PC Speaker Support"
> 
> When booting, it is "enumerated" as an input device: (from dmesg)
> 
>   input: PC Speaker as /devices/platform/pcspkr/input/input2
> 
> Just trying to figure out the rationale behind the choice...

The last time around for this question, I was half-paying attention, and
the rationale sounded like "We had an input device framework, no output
device framework, and too many bad shrooms to do something comprehensible".

(This is such a *frequent* FAQ, even all the time since 2.6.0 escaped, that
maybe we need to add a 3-4 line explain to the Kconfig 'help' stanza for
CONFIG_INPUT_PCSPKR - although for some reason, INPUT_SPARCSPKR and
INPUT_M68K_BEEP don't seem to cause the same questions....)


[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]

  parent reply	other threads:[~2008-02-15 21:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-15 21:19 Linda Walsh
2008-02-15 21:49 ` Jiri Slaby
2008-02-15 21:55 ` Valdis.Kletnieks [this message]
2008-02-15 23:18   ` Linda Walsh

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=4387.1203112503@turing-police.cc.vt.edu \
    --to=valdis.kletnieks@vt.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@tlinx.org \
    --subject='Re: x86-32-config: why is pc-speaker an input device?' \
    /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

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).