What exactly does CONFIG_INPUT_KEYBDEV do?
I found that _not_setting it, 2.4.31 still looks for keyboard at boot:
Oct 9 10:41:49 kernel: keyboard: Timeout - AT keyboard not present?(ed)
Oct 9 10:41:50 kernel: keyboard: Timeout - AT keyboard not present?(f4)
and doing a find/grep in the code reveals that CONFIG_INPUT_KEYBDEV doesn't
seem to do anything anywhere except def/undef itself:
[[email protected]]# find . -name \*.h -exec grep -iHn "INPUT_KEYBDEV" {} \;
./include/linux/autoconf.h:482:#undef CONFIG_INPUT_KEYBDEV
./include/config/input/keybdev.h:1:#undef CONFIG_INPUT_KEYBDEV
[[email protected]]# find . -name \*.c -exec grep -iHn "INPUT_KEYBDEV" {} \;
... nothing...
Therefore I still have to manually edit include/linux/pc_keyb.h to undef the
(no) keyboard timeouts:
?
Nick
--
http://sourceforge.net/projects/quake2plus
"When you're chewing on life's gristle,
Don't grumble, Give a whistle..."
On Sun, 09 Oct 2005 11:41:10 BST, Nick Warne said:
> What exactly does CONFIG_INPUT_KEYBDEV do?
>
> I found that _not_setting it, 2.4.31 still looks for keyboard at boot:
>
> Oct 9 10:41:49 kernel: keyboard: Timeout - AT keyboard not present?(ed)
> Oct 9 10:41:50 kernel: keyboard: Timeout - AT keyboard not present?(f4)
>
> and doing a find/grep in the code reveals that CONFIG_INPUT_KEYBDEV doesn't
> seem to do anything anywhere except def/undef itself:
>
>
> [[email protected]]# find . -name \*.h -exec grep -iHn "INPUT_KEYBDEV" {} \;
Try grepping through the *Makefiles* for that. In many cases, a CONFIG_FOO
variable is used to control whether a given .c is compiled into a .o for
inclusion in the kernel.
On Sun, Oct 09, 2005 at 11:41:10AM +0100, Nick Warne wrote:
> What exactly does CONFIG_INPUT_KEYBDEV do?
It's used to link keybdev.o in drivers/input/Makefile, and to resolve a
few dependencies for other config options (HIL) in some hil/Config.in.
> I found that _not_setting it, 2.4.31 still looks for keyboard at boot:
>
> Oct 9 10:41:49 kernel: keyboard: Timeout - AT keyboard not present?(ed)
> Oct 9 10:41:50 kernel: keyboard: Timeout - AT keyboard not present?(f4)
(...)
> Therefore I still have to manually edit include/linux/pc_keyb.h to undef the
> (no) keyboard timeouts:
This option is not used for pc_keyb.c inclusion which is linked unless you
set CONFIG_DUMMY_KEYB (check drivers/char/Makefile for this), in which case
you'll use dummy_keyb.c which was made exactly for your usage.
Cheers,
Willy
On Sunday 09 October 2005 21:40, Willy Tarreau wrote:
> > Oct 9 10:41:49 kernel: keyboard: Timeout - AT keyboard not present?(ed)
> > Oct 9 10:41:50 kernel: keyboard: Timeout - AT keyboard not present?(f4)
>
> (...)
>
> > Therefore I still have to manually edit include/linux/pc_keyb.h to undef
> > the (no) keyboard timeouts:
>
> This option is not used for pc_keyb.c inclusion which is linked unless you
> set CONFIG_DUMMY_KEYB (check drivers/char/Makefile for this), in which case
> you'll use dummy_keyb.c which was made exactly for your usage.
OK, thanks, but I am still confused. I had to add CONFIG_DUMMY_KEYB=y
manually (i386), as nowhere could I find an option in menuconfig (and
find/grep revealed nothing either)...
This now boots with no keyboard warnings, as suggested (after I removed keymap
etc. from start scripts). But I still think I done it all wrong?
Nick
--
http://sourceforge.net/projects/quake2plus
"When you're chewing on life's gristle,
Don't grumble, Give a whistle..."
On Mon, Oct 10, 2005 at 07:24:02PM +0100, Nick Warne wrote:
> On Sunday 09 October 2005 21:40, Willy Tarreau wrote:
>
> > > Oct 9 10:41:49 kernel: keyboard: Timeout - AT keyboard not present?(ed)
> > > Oct 9 10:41:50 kernel: keyboard: Timeout - AT keyboard not present?(f4)
> >
> > (...)
> >
> > > Therefore I still have to manually edit include/linux/pc_keyb.h to undef
> > > the (no) keyboard timeouts:
> >
> > This option is not used for pc_keyb.c inclusion which is linked unless you
> > set CONFIG_DUMMY_KEYB (check drivers/char/Makefile for this), in which case
> > you'll use dummy_keyb.c which was made exactly for your usage.
>
> OK, thanks, but I am still confused. I had to add CONFIG_DUMMY_KEYB=y
> manually (i386), as nowhere could I find an option in menuconfig (and
> find/grep revealed nothing either)...
>
> This now boots with no keyboard warnings, as suggested (after I removed keymap
> etc. from start scripts). But I still think I done it all wrong?
Not necessarily, it may be that too few people use it and the option has
vanished from any config. You can provide a patch to re-enable it if you
want. In this case, please also provide a little help in Configure.help.
Regards,
Willy