Hi,
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@aether:~$ 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
...
I'm using the 2.6.17 kernel (it is an Ubuntu kernel though).
With friendly regards,
Takis
On Mon, 2006-10-23 20:32:55 +0200, Panagiotis Issaris <[email protected]> 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@aether:~$ 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 [email protected] +49-172-7608481
Signature of: Lauf nicht vor Deinem Glück davon:
the second : Es könnte hinter Dir stehen!
>
>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'
--