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

Message-ID: <Pine.LNX.4.61.0610241546100.19278@yvahk01.tjqt.qr>
Date:	Tue, 24 Oct 2006 15:47:34 +0200 (MEST)
From:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
To:	Jan-Benedict Glaw <jbglaw@...-owl.de>
cc:	Panagiotis Issaris <panagiotis@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: PC speaker listed as input device

>
>The Input subsystem also covers simple beeps, because real keyboards
>beep.  So it was only straight-forward to also put the PC speaker into

"What is real?" -from Matrix

That said, older keyboards, such as SUN4, do indeed beep themselves. In fact,
it's just a matter where the beeper is installed, even on x86, you can see the
history of it, because the IO port for beeps is the same as for keyboard leds.


	-`J'
-- 
-
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/