I enabled a couple new kernel modules as loadable (m
as opposed to builtin with y
) but do not understand how the CONFIG maps to the .ko file.
modprobe CONFIG_MY_CONFIG
insmod CONFIG_MY_CONFIG
modprobe MY_CONFIG
insmod MY_CONFIG
I enabled a couple new kernel modules as loadable (m
as opposed to builtin with y
) but do not understand how the CONFIG maps to the .ko file.
modprobe CONFIG_MY_CONFIG
insmod CONFIG_MY_CONFIG
modprobe MY_CONFIG
insmod MY_CONFIG
Firstly, you need to find usage of
CONFIG_<MYCONFIG>
variable in one ofMakefile
's (except the top one). You may usegrep
utility for this (run from kernel source directory):Line with that usage normally looks like
Here
<driver>
is the name of the driver used bymodprobe
:For find exact path to the driver you may use
--show-depends
option for modprobe:Makefile's used in Linux kernel are described in Documentation/kbuild/makefiles.txt.