The configuration of the kernel is determined by the configuration options in the form of config prefixed with the config_feature.
The configuration options determine the following two areas:
1) which files are compiled
2) What code is processed by the preprocessor directive
Configuration options control the compilation process with the BOOL option and the TriState option. The value of the BOOL option is yes and the value of the No,tristate option
Yes, no, module. When you select module, the code is compiled into a module that can be dynamically loaded into the kernel. When you select Yes, the code is displayed in the
Compiled into the kernel image instead of as a loadable module. Device-driven code is typically tristate with configuration options.
The configuration option can also be a string or an int. These control options do not control the kernel's compilation process, but are used by the kernel as a preprocessing macro.
The delivery of the value.
The kernel provides a variety of configuration tools to facilitate configuration of kernel-related code:
make Config
The tool iterates through each of the configuration options, each of which will be asking the user and selecting their values by the user. The tool takes up a lot of user time.
Developers are often advised to use ncurses-based graphical tools:
make Menuconfig
When the configuration is complete, a. config file is generated at the root of the kernel source code.
The following is a sample of the kernel configuration using the Freescale imx6:
Make // Clean kernel Configurations Make // Config kernel Make // Generate Uimage Make // Generate Modules
Linux kernel configuration