linux-kernel - Re: PC speaker listed as input device

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-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 24 Oct 2006 10:38:21 +0200
From:	Jan-Benedict Glaw <jbglaw@...-owl.de>
To:	Panagiotis Issaris <panagiotis@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: PC speaker listed as input device

On Mon, 2006-10-23 20:32:55 +0200, Panagiotis Issaris <panagiotis@...il.com> wrote:
> While trying to get my Hauppauge's remote control working, I noticed that my
> PC speaker is getting recognized as an input device. This seems very weird
> to me, is there some logic behind this?
> 
> takis@...her:~$ cat /proc/bus/input/devices
> I: Bus=0010 Vendor=001f Product=0001 Version=0100
> N: Name="PC Speaker"
> P: Phys=isa0061/input0
> S: Sysfs=/class/input/input0
> H: Handlers=kbd event0
> B: EV=40001
> B: SND=6
> ...

The Input subsystem also covers simple beeps, because real keyboards
beep.  So it was only straight-forward to also put the PC speaker into
the Input subsystem to be able to emulate real keyboard's beeps as
good as possible :)

MfG, JBG

-- 
      Jan-Benedict Glaw      jbglaw@...-owl.de              +49-172-7608481
  Signature of:                        Lauf nicht vor Deinem Glück davon:
  the second  :                             Es könnte hinter Dir stehen!

Download attachment "signature.asc" of type "application/pgp-signature" (190 bytes)