Check if specific functionally is built into the kernel
Dear all, I have the following problem. Some functionality can be either built into the kernel or it can be build as a module. In the latter case the application should load the module. Is there a general approach to test if specific functionality is built statically or as a module? Thanks Arokux
On Sun, Feb 26, 2012 at 7:08 PM, Arokux B. <arokux@gmail.com> wrote:
Dear all,
I have the following problem. Some functionality can be either built into the kernel or it can be build as a module. In the latter case the application should load the module.
Is there a general approach to test if specific functionality is built statically or as a module?
If available, you can check .config file. (e.g check if CONFIG_X_OPTION=Y or CONFIG_X_OPTION=m). thanks, Daniel.
On Sun, Feb 26, 2012 at 7:26 PM, Daniel Baluta <daniel.baluta@gmail.com> wrote:
On Sun, Feb 26, 2012 at 7:08 PM, Arokux B. <arokux@gmail.com> wrote:
Dear all,
I have the following problem. Some functionality can be either built into the kernel or it can be build as a module. In the latter case the application should load the module.
Is there a general approach to test if specific functionality is built statically or as a module?
If available, you can check .config file. (e.g check if CONFIG_X_OPTION=Y or CONFIG_X_OPTION=m).
If you don't have your .config (distro prebuilt image), you can check /proc/config.gz or /boot/ for a config which corresponds to your uname -r. Vlad
participants (3)
-
Arokux B. -
Daniel Baluta -
Vlad Dogaru