3 messages, 3 authors, 2012-02-26 · open the first message on its own page
From: Arokux B. <hidden>
Date: 2012-02-26 17:08:02
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
From: Daniel Baluta <hidden>
Date: 2012-02-26 17:26:42
On Sun, Feb 26, 2012 at 7:08 PM, Arokux B. [off-list ref] 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.
From: Vlad Dogaru <hidden>
Date: 2012-02-26 21:13:51
On Sun, Feb 26, 2012 at 7:26 PM, Daniel Baluta [off-list ref] wrote:
On Sun, Feb 26, 2012 at 7:08 PM, Arokux B. [off-list ref] wrote:quoted
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