From: Derrick W. <de...@lo...> - 2004-03-26 15:34:17
|
It appears that the KIOCSOUND ioctl call is broken in the 2.6 kernels. KIOSOUND calls kd_nosound() and kd_mksound() in linux/drivers/char/keyboard.c to emit sound. These functions do not appear to be working, I am quickly trying to learn the input API and how the input_event() request that kd_mksound() calls is failing. However there is very little documentation on the subject, and because I'm not familiar with input devices the code is confusing. For example, in kd_mksound() the code loops thru a list of (I'm assuming) keyboard devices, looking for one that has the EV_SND bit turned on. But it never finds any. So I'm attempting to find where the handle->dev->evbit bit is set. I'm assuming that would be when the input device is registered with the input API, but I cannot seam to find it!! Any assistance would be greatly appreciated. -- D E R R I C K J. W I P P L E R Logical Solutions, Inc. Software Developer <de...@lo...> 'I generally avoid temptation unless I can't resist it." -- Mae West |
From: Vojtech P. <vo...@su...> - 2004-03-26 16:00:31
|
On Fri, Mar 26, 2004 at 10:29:57AM -0500, Derrick Wippler wrote: > It appears that the KIOCSOUND ioctl call is broken in the 2.6 kernels. > KIOSOUND calls kd_nosound() and kd_mksound() in linux/drivers/char/keyboard.c > to emit sound. These functions do not appear to be working, I am quickly > trying to learn the input API and how the input_event() request that > kd_mksound() calls is failing. However there is very little documentation on > the subject, and because I'm not familiar with input devices the code is > confusing. > > For example, in kd_mksound() the code loops thru a list of (I'm assuming) > keyboard devices, looking for one that has the EV_SND bit turned on. But it > never finds any. So I'm attempting to find where the handle->dev->evbit bit > is set. I'm assuming that would be when the input device is registered with > the input API, but I cannot seam to find it!! > > Any assistance would be greatly appreciated. You probably should enable the PC Speaker driver under Input/Misc. -- Vojtech Pavlik SuSE Labs, SuSE CR |
From: Derrick W. <de...@lo...> - 2004-03-26 16:14:51
|
On Friday 26 March 2004 11:01 am, you wrote: > On Fri, Mar 26, 2004 at 10:29:57AM -0500, Derrick Wippler wrote: > > It appears that the KIOCSOUND ioctl call is broken in the 2.6 kernels. > > KIOSOUND calls kd_nosound() and kd_mksound() in > > linux/drivers/char/keyboard.c to emit sound. These functions do not > > appear to be working, I am quickly trying to learn the input API and how > > the input_event() request that kd_mksound() calls is failing. However > > there is very little documentation on the subject, and because I'm not > > familiar with input devices the code is confusing. > > > > For example, in kd_mksound() the code loops thru a list of (I'm assuming) > > keyboard devices, looking for one that has the EV_SND bit turned on. But > > it never finds any. So I'm attempting to find where the > > handle->dev->evbit bit is set. I'm assuming that would be when the input > > device is registered with the input API, but I cannot seam to find it!! > > > > Any assistance would be greatly appreciated. > > You probably should enable the PC Speaker driver under Input/Misc. That is very obscure!! Why would PC speaker support be an kernel option? I performed a very thorough search of the config options. Even using this command the search the Kconfig's # for i in `find | grep Kconfig`; do echo $i;fgrep "speaker" $i;done if only I had greped for "Speaker" instead of "speaker". Grrrr!!!! What a waste of time!!!!! (1 full day, before e-mailing for help). Thanks tho !!!! -- D E R R I C K J. W I P P L E R Logical Solutions, Inc. Software Developer <de...@lo...> Sex is a natural bodily process, like a stroke. |
From: James S. <jsi...@in...> - 2004-03-26 17:41:21
|
> That is very obscure!! Why would PC speaker support be an kernel option? On some platforms the speaker is built into the keyboard. |
From: Derrick W. <de...@lo...> - 2004-03-26 17:58:30
|
Then shouldn't the PC speaker config option be ON as default? Most keyboard's today do not have PC speakers or "beepers" in them. Wouldn't that be a reasonable default? On Friday 26 March 2004 12:41 pm, James Simmons wrote: > > That is very obscure!! Why would PC speaker support be an kernel option? > > On some platforms the speaker is built into the keyboard. > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > Linuxconsole-dev mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linuxconsole-dev -- D E R R I C K J. W I P P L E R Logical Solutions, Inc. Software Developer <de...@lo...> Before Xerox, five carbons were the maximum extension of anybody's ego. |
From: James S. <jsi...@in...> - 2004-03-26 18:28:11
|
> Then shouldn't the PC speaker config option be ON as default? > Most keyboard's today do not have PC speakers or "beepers" in them. > Wouldn't that be a reasonable default? I agree. I have no idea why Linus made the default to be off. Perhaps we should send a updated default config with the PC speaker set to on to linus. |