Messages in this thread | | | From | Neil Brown <> | Date | Mon, 21 Jul 2003 09:48:48 +1000 | Subject | RE: "Where's the Beep?" (PCMCIA/vt_ioctl-s) |
| |
On Thursday July 17, Riley@Williams.Name wrote: > Hi James. > > >>>> On my old DELL LM laptop the -2.5 series no longer issues > >>>> any beeps when a card is inserted. The problem is in the > >>>> kernel, as the test program below (extracted from cardmgr) > >>>> beeps on -2.4, but not on -2.5. > > >>> CONFIG_INPUT_PCSPKR needs to be =y (or =m and the module > >>> loaded). > > >> That's true, but I wonder why PC Speaker is under *INPUT* > >> category... > > > Because many keyboards have built in speakers. > > What sort of logic is that !!! > > The ONLY reason I can think of for treating a speaker as an INPUT > device is if that speaker is wired up in a way that allows it to > be used as a microphone, the way some baby-intercoms do. If this > is the reason, then don't expect any sort of quality from it, and > please also separate this use from the more conventional one.
The problem here is really with the name 'INPUT'. It is not an 'input' subsytem, but rather an 'event' subsystem. It handles events like key presses, mounts movements, speaker beeps, LED on/off etc.
It could quite reasonable also be used for APCI events like power status changes and power-button events, but I don't know that anyone has any plans for that.
I gather the event subsystem was conceived to help managed the wide variety of input devices (USB, PS/2, serial, etc) and was inadvertantly misnamed 'input'.
find linux -type f | xargs perl -pi -e 's/input/event/i'
or something like that :-)
NeilBrown - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |