lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <47B601CF.9070300@tlinx.org>
Date:	Fri, 15 Feb 2008 13:19:11 -0800
From:	Linda Walsh <lkml@...nx.org>
To:	LKML <linux-kernel@...r.kernel.org>
Subject: x86-32-config: why is pc-speaker an input device?

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ