LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
* x86-32-config: why is pc-speaker an input device?
@ 2008-02-15 21:19 Linda Walsh
  2008-02-15 21:49 ` Jiri Slaby
  2008-02-15 21:55 ` Valdis.Kletnieks
  0 siblings, 2 replies; 4+ messages in thread
From: Linda Walsh @ 2008-02-15 21:19 UTC (permalink / raw)
  To: LKML

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


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: x86-32-config: why is pc-speaker an input device?
  2008-02-15 21:19 x86-32-config: why is pc-speaker an input device? Linda Walsh
@ 2008-02-15 21:49 ` Jiri Slaby
  2008-02-15 21:55 ` Valdis.Kletnieks
  1 sibling, 0 replies; 4+ messages in thread
From: Jiri Slaby @ 2008-02-15 21:49 UTC (permalink / raw)
  To: Linda Walsh; +Cc: LKML

On 02/15/2008 10:19 PM, Linda Walsh wrote:
> 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...

Again :)

Search archives...

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: x86-32-config: why is pc-speaker an input device?
  2008-02-15 21:19 x86-32-config: why is pc-speaker an input device? Linda Walsh
  2008-02-15 21:49 ` Jiri Slaby
@ 2008-02-15 21:55 ` Valdis.Kletnieks
  2008-02-15 23:18   ` Linda Walsh
  1 sibling, 1 reply; 4+ messages in thread
From: Valdis.Kletnieks @ 2008-02-15 21:55 UTC (permalink / raw)
  To: Linda Walsh; +Cc: LKML

[-- 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 --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: x86-32-config: why is pc-speaker an input device?
  2008-02-15 21:55 ` Valdis.Kletnieks
@ 2008-02-15 23:18   ` Linda Walsh
  0 siblings, 0 replies; 4+ messages in thread
From: Linda Walsh @ 2008-02-15 23:18 UTC (permalink / raw)
  To: Valdis.Kletnieks; +Cc: LKML

Valdis.Kletnieks@vt.edu wrote:
> 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".
>   
---
    Yeah, hmm...the question I'd have then is the "only" output device 
that doesn't fit into a better category? 

    Could there be other OUTput devices in this category?   Would
renaming the category to something like "Miscellaneous I/O Devices" be
reasonable?    Are keyboard status lights considered output devices?
Are "force-feedback" devices meaning devices like a rumble-gamepad
device?  Isn't that providing output via feedback?

    Though, I would agree, most of these devices would be thought of
as "input" devices. Dang PC-SPEAKER...um...since the driver is config'ed
with the 'input' interface, dang, it really seems like it should be an
entry under sound.

    I can see the problem and I'm not familiar enough with the underlying
drivers to know how the PC-Speaker would best be handled. 

> (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....)
>   
----
No matter where it is in the 'kernel configuration', it sure seems
strange (in "user land"), to see the PC-Speaker be recognized as an
input device -- especially in light of the fact that "all speakers
are microphones" (http://www.zyra.org.uk/sp-mic.htm).  Would some user
wonder whether or not their speaker has some dual-circuitry to listen
as well as output (ala TV sets being 2-way video devices in Max Headroom)?




^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2008-02-15 23:19 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2008-02-15 21:19 x86-32-config: why is pc-speaker an input device? Linda Walsh
2008-02-15 21:49 ` Jiri Slaby
2008-02-15 21:55 ` Valdis.Kletnieks
2008-02-15 23:18   ` Linda Walsh

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