| CptDondo 2005-10-05, 8:56 pm |
| I'm not really sure what problem I have but....
I am trying to compile a kernel for arm architecture. I need to use the
uinput modules, including keybdev.
When I try to modprobe keybdev I get:
/lib/modules/2.4.26-ys/kernel/drivers/input/keybdev.o: unresolved symbol
handle_scancode
/lib/modules/2.4.26-ys/kernel/drivers/input/keybdev.o: unresolved symbol
keyboard_tasklet
/lib/modules/2.4.26-ys/kernel/drivers/input/keybdev.o: unresolved symbol
kbd_ledfunc
/lib/modules/2.4.26-ys/kernel/drivers/input/keybdev.o: unresolved symbol
kbd_refresh_leds
/lib/modules/2.4.26-ys/kernel/drivers/input/keybdev.o: insmod
/lib/modules/2.4.26-ys/kernel/drived/lib/modules/2.4.26-ys/kernel/drivers/input/keybdev.o:
insmod keybdev failed
The bit of code that exports those symbols is in drivers/char/keyboard.c
and even exports those symbols:
EXPORT_SYMBOL(handle_scancode);
EXPORT_SYMBOL(kbd_ledfunc);
EXPORT_SYMBOL(kbd_refresh_leds);
So the only thing I can think of is that something (the linker???) is
not hooking up keybdev to the symbols exported by keyboard....
I know next to nothing about how the various dependencies and symbols
are resolved during a kernel build and module inserts.... But clearly
the code is there, the symbols should be there, but the module is not
seeing them.
Are there any commands that would let me see the kernel symbols that are
exported?
Or perhaps can I modify the Makefile(s) to tell the kernel it needs to
make that connection?
(And no I cannot change to a newer kernel.... It's a highly modified
kernel for a particular piece of hardware I am working with....)
|