kconfig.txt 6.6 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192
  1. This file contains some assistance for using "make *config".
  2. Use "make help" to list all of the possible configuration targets.
  3. The xconfig ('qconf') and menuconfig ('mconf') programs also
  4. have embedded help text. Be sure to check it for navigation,
  5. search, and other general help text.
  6. ======================================================================
  7. General
  8. --------------------------------------------------
  9. New kernel releases often introduce new config symbols. Often more
  10. important, new kernel releases may rename config symbols. When
  11. this happens, using a previously working .config file and running
  12. "make oldconfig" won't necessarily produce a working new kernel
  13. for you, so you may find that you need to see what NEW kernel
  14. symbols have been introduced.
  15. To see a list of new config symbols when using "make oldconfig", use
  16. cp user/some/old.config .config
  17. yes "" | make oldconfig >conf.new
  18. and the config program will list as (NEW) any new symbols that have
  19. unknown values. Of course, the .config file is also updated with
  20. new (default) values, so you can use:
  21. grep "(NEW)" conf.new
  22. to see the new config symbols or you can use diffconfig to see the
  23. differences between the previous and new .config files:
  24. scripts/diffconfig .config.old .config | less
  25. ______________________________________________________________________
  26. Environment variables for '*config'
  27. KCONFIG_CONFIG
  28. --------------------------------------------------
  29. This environment variable can be used to specify a default kernel config
  30. file name to override the default name of ".config".
  31. KCONFIG_OVERWRITECONFIG
  32. --------------------------------------------------
  33. If you set KCONFIG_OVERWRITECONFIG in the environment, Kconfig will not
  34. break symlinks when .config is a symlink to somewhere else.
  35. ______________________________________________________________________
  36. Environment variables for '{allyes/allmod/allno/rand}config'
  37. KCONFIG_ALLCONFIG
  38. --------------------------------------------------
  39. (partially based on lkml email from/by Rob Landley, re: miniconfig)
  40. --------------------------------------------------
  41. The allyesconfig/allmodconfig/allnoconfig/randconfig variants can
  42. also use the environment variable KCONFIG_ALLCONFIG as a flag or a
  43. filename that contains config symbols that the user requires to be
  44. set to a specific value. If KCONFIG_ALLCONFIG is used without a
  45. filename, "make *config" checks for a file named
  46. "all{yes/mod/no/def/random}.config" (corresponding to the *config command
  47. that was used) for symbol values that are to be forced. If this file
  48. is not found, it checks for a file named "all.config" to contain forced
  49. values.
  50. This enables you to create "miniature" config (miniconfig) or custom
  51. config files containing just the config symbols that you are interested
  52. in. Then the kernel config system generates the full .config file,
  53. including symbols of your miniconfig file.
  54. This 'KCONFIG_ALLCONFIG' file is a config file which contains
  55. (usually a subset of all) preset config symbols. These variable
  56. settings are still subject to normal dependency checks.
  57. Examples:
  58. KCONFIG_ALLCONFIG=custom-notebook.config make allnoconfig
  59. or
  60. KCONFIG_ALLCONFIG=mini.config make allnoconfig
  61. or
  62. make KCONFIG_ALLCONFIG=mini.config allnoconfig
  63. These examples will disable most options (allnoconfig) but enable or
  64. disable the options that are explicitly listed in the specified
  65. mini-config files.
  66. ______________________________________________________________________
  67. Environment variables for 'silentoldconfig'
  68. KCONFIG_NOSILENTUPDATE
  69. --------------------------------------------------
  70. If this variable has a non-blank value, it prevents silent kernel
  71. config updates (requires explicit updates).
  72. KCONFIG_AUTOCONFIG
  73. --------------------------------------------------
  74. This environment variable can be set to specify the path & name of the
  75. "auto.conf" file. Its default value is "include/config/auto.conf".
  76. KCONFIG_TRISTATE
  77. --------------------------------------------------
  78. This environment variable can be set to specify the path & name of the
  79. "tristate.conf" file. Its default value is "include/config/tristate.conf".
  80. KCONFIG_AUTOHEADER
  81. --------------------------------------------------
  82. This environment variable can be set to specify the path & name of the
  83. "autoconf.h" (header) file.
  84. Its default value is "include/generated/autoconf.h".
  85. ======================================================================
  86. menuconfig
  87. --------------------------------------------------
  88. SEARCHING for CONFIG symbols
  89. Searching in menuconfig:
  90. The Search function searches for kernel configuration symbol
  91. names, so you have to know something close to what you are
  92. looking for.
  93. Example:
  94. /hotplug
  95. This lists all config symbols that contain "hotplug",
  96. e.g., HOTPLUG, HOTPLUG_CPU, MEMORY_HOTPLUG.
  97. For search help, enter / followed TAB-TAB-TAB (to highlight
  98. <Help>) and Enter. This will tell you that you can also use
  99. regular expressions (regexes) in the search string, so if you
  100. are not interested in MEMORY_HOTPLUG, you could try
  101. /^hotplug
  102. ______________________________________________________________________
  103. User interface options for 'menuconfig'
  104. MENUCONFIG_COLOR
  105. --------------------------------------------------
  106. It is possible to select different color themes using the variable
  107. MENUCONFIG_COLOR. To select a theme use:
  108. make MENUCONFIG_COLOR=<theme> menuconfig
  109. Available themes are:
  110. mono => selects colors suitable for monochrome displays
  111. blackbg => selects a color scheme with black background
  112. classic => theme with blue background. The classic look
  113. bluetitle => a LCD friendly version of classic. (default)
  114. MENUCONFIG_MODE
  115. --------------------------------------------------
  116. This mode shows all sub-menus in one large tree.
  117. Example:
  118. make MENUCONFIG_MODE=single_menu menuconfig
  119. ======================================================================
  120. xconfig
  121. --------------------------------------------------
  122. Searching in xconfig:
  123. The Search function searches for kernel configuration symbol
  124. names, so you have to know something close to what you are
  125. looking for.
  126. Example:
  127. Ctrl-F hotplug
  128. or
  129. Menu: File, Search, hotplug
  130. lists all config symbol entries that contain "hotplug" in
  131. the symbol name. In this Search dialog, you may change the
  132. config setting for any of the entries that are not grayed out.
  133. You can also enter a different search string without having
  134. to return to the main menu.
  135. ======================================================================
  136. gconfig
  137. --------------------------------------------------
  138. Searching in gconfig:
  139. None (gconfig isn't maintained as well as xconfig or menuconfig);
  140. however, gconfig does have a few more viewing choices than
  141. xconfig does.
  142. ###