€•Œsphinx.addnodes”Œdocument”“”)�”}”(Œ rawsource”Œ”Œchildren”]”(Œ translations”Œ LanguagesNode”“”)�”}”(hhh]”(hŒ pending_xref”“”)�”}”(hhh]”Œdocutils.nodes”ŒText”“”ŒChinese (Simplified)”…”�”}”Œparent”hsbaŒ attributes”}”(Œids”]”Œclasses”]”Œnames”]”Œdupnames”]”Œbackrefs”]”Œ refdomain”Œstd”Œreftype”Œdoc”Œ reftarget”Œ+/translations/zh_CN/kbuild/kconfig-language”Œmodname”NŒ classname”NŒ refexplicit”ˆuŒtagname”hhh ubh)�”}”(hhh]”hŒChinese (Traditional)”…”�”}”hh2sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ+/translations/zh_TW/kbuild/kconfig-language”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)�”}”(hhh]”hŒItalian”…”�”}”hhFsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ+/translations/it_IT/kbuild/kconfig-language”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)�”}”(hhh]”hŒJapanese”…”�”}”hhZsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ+/translations/ja_JP/kbuild/kconfig-language”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)�”}”(hhh]”hŒKorean”…”�”}”hhnsbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ+/translations/ko_KR/kbuild/kconfig-language”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)�”}”(hhh]”hŒPortuguese (Brazilian)”…”�”}”hh‚sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ+/translations/pt_BR/kbuild/kconfig-language”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubh)�”}”(hhh]”hŒSpanish”…”�”}”hh–sbah}”(h]”h ]”h"]”h$]”h&]”Œ refdomain”h)Œreftype”h+Œ reftarget”Œ+/translations/sp_SP/kbuild/kconfig-language”Œmodname”NŒ classname”NŒ refexplicit”ˆuh1hhh ubeh}”(h]”h ]”h"]”h$]”h&]”Œcurrent_language”ŒEnglish”uh1h hhŒ _document”hŒsource”NŒline”NubhŒsection”“”)�”}”(hhh]”(hŒtitle”“”)�”}”(hŒKconfig Language”h]”hŒKconfig Language”…”�”}”(hh¼h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhh·h²hh³ŒE/var/lib/git/docbuild/linux/Documentation/kbuild/kconfig-language.rst”h´Kubh¶)�”}”(hhh]”(h»)�”}”(hŒ Introduction”h]”hŒ Introduction”…”�”}”(hhÎh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhhËh²hh³hÊh´KubhŒ paragraph”“”)�”}”(hŒcThe configuration database is a collection of configuration options organized in a tree structure::”h]”hŒbThe configuration database is a collection of configuration options organized in a tree structure:”…”�”}”(hhÞh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KhhËh²hubhŒ literal_block”“”)�”}”(hXe+- Code maturity level options | +- Prompt for development and/or incomplete code/drivers +- General setup | +- Networking support | +- System V IPC | +- BSD Process Accounting | +- Sysctl support +- Loadable module support | +- Enable loadable module support | +- Set version information on all module symbols | +- Kernel module loader +- ...”h]”hXe+- Code maturity level options | +- Prompt for development and/or incomplete code/drivers +- General setup | +- Networking support | +- System V IPC | +- BSD Process Accounting | +- Sysctl support +- Loadable module support | +- Enable loadable module support | +- Set version information on all module symbols | +- Kernel module loader +- ...”…”�”}”hhîsbah}”(h]”h ]”h"]”h$]”h&]”Œ xml:space”Œpreserve”uh1hìh³hÊh´K hhËh²hubhÝ)�”}”(hŒ¯Every entry has its own dependencies. These dependencies are used to determine the visibility of an entry. Any child entry is only visible if its parent entry is also visible.”h]”hŒ¯Every entry has its own dependencies. These dependencies are used to determine the visibility of an entry. Any child entry is only visible if its parent entry is also visible.”…”�”}”(hhþh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KhhËh²hubeh}”(h]”Œ introduction”ah ]”h"]”Œ introduction”ah$]”h&]”uh1hµhh·h²hh³hÊh´Kubh¶)�”}”(hhh]”(h»)�”}”(hŒ Menu entries”h]”hŒ Menu entries”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjh²hh³hÊh´KubhÝ)�”}”(hŒ‚Most entries define a config option; all other entries help to organize them. A single configuration option is defined like this::”h]”hŒ�Most entries define a config option; all other entries help to organize them. A single configuration option is defined like this:”…”�”}”(hj%h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Khjh²hubhí)�”}”(hŒÒconfig MODVERSIONS bool "Set version information on all module symbols" depends on MODULES help Usually, modules have to be recompiled whenever you switch to a new kernel. ...”h]”hŒÒconfig MODVERSIONS bool "Set version information on all module symbols" depends on MODULES help Usually, modules have to be recompiled whenever you switch to a new kernel. ...”…”�”}”hj3sbah}”(h]”h ]”h"]”h$]”h&]”hühýuh1hìh³hÊh´K"hjh²hubhÝ)�”}”(hXµEvery line starts with a key word and can be followed by multiple arguments. "config" starts a new config entry. The following lines define attributes for this config option. Attributes can be the type of the config option, input prompt, dependencies, help text and default values. A config option can be defined multiple times with the same name, but every definition can have only a single input prompt and the type must not conflict.”h]”hX¹Every line starts with a key word and can be followed by multiple arguments. “configâ€� starts a new config entry. The following lines define attributes for this config option. Attributes can be the type of the config option, input prompt, dependencies, help text and default values. A config option can be defined multiple times with the same name, but every definition can have only a single input prompt and the type must not conflict.”…”�”}”(hjAh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´K)hjh²hubeh}”(h]”Œ menu-entries”ah ]”h"]”Œ menu entries”ah$]”h&]”uh1hµhh·h²hh³hÊh´Kubh¶)�”}”(hhh]”(h»)�”}”(hŒMenu attributes”h]”hŒMenu attributes”…”�”}”(hjZh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjWh²hh³hÊh´K2ubhÝ)�”}”(hŒeA menu entry can have a number of attributes. Not all of them are applicable everywhere (see syntax).”h]”hŒeA menu entry can have a number of attributes. Not all of them are applicable everywhere (see syntax).”…”�”}”(hjhh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´K4hjWh²hubhŒ bullet_list”“”)�”}”(hhh]”(hŒ list_item”“”)�”}”(hXqtype definition: "bool"/"tristate"/"string"/"hex"/"int" Every config option must have a type. There are only two basic types: tristate and string; the other types are based on these two. The type definition optionally accepts an input prompt, so these two examples are equivalent:: bool "Networking support" and:: bool prompt "Networking support" ”h]”(hÝ)�”}”(hŒ7type definition: "bool"/"tristate"/"string"/"hex"/"int"”h]”hŒKtype definition: “boolâ€�/â€�tristateâ€�/â€�stringâ€�/â€�hexâ€�/â€�intâ€�”…”�”}”(hj�h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´K7hj}ubhÝ)�”}”(hŒáEvery config option must have a type. There are only two basic types: tristate and string; the other types are based on these two. The type definition optionally accepts an input prompt, so these two examples are equivalent::”h]”hŒàEvery config option must have a type. There are only two basic types: tristate and string; the other types are based on these two. The type definition optionally accepts an input prompt, so these two examples are equivalent:”…”�”}”(hj�h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´K9hj}ubhí)�”}”(hŒbool "Networking support"”h]”hŒbool "Networking support"”…”�”}”hj�sbah}”(h]”h ]”h"]”h$]”h&]”hühýuh1hìh³hÊh´K>hj}ubhÝ)�”}”(hŒand::”h]”hŒand:”…”�”}”(hj«h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´K@hj}ubhí)�”}”(hŒ bool prompt "Networking support"”h]”hŒ bool prompt "Networking support"”…”�”}”hj¹sbah}”(h]”h ]”h"]”h$]”h&]”hühýuh1hìh³hÊh´KBhj}ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j{hjxh²hh³hÊh´Nubj|)�”}”(hXêinput prompt: "prompt" ["if" ] Every menu entry can have at most one prompt, which is used to display to the user. Optionally dependencies only for this prompt can be added with "if". If a prompt is not present, the config option is a non-visible symbol, meaning its value cannot be directly changed by the user (such as altering the value in ``.config``) and the option will not appear in any config menus. Its value can only be set via "default" and "select" (see below). ”h]”(hÝ)�”}”(hŒ-input prompt: "prompt" ["if" ]”h]”hŒ5input prompt: “promptâ€� [“ifâ€� ]”…”�”}”(hjÑh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KEhjÍubhÝ)�”}”(hXºEvery menu entry can have at most one prompt, which is used to display to the user. Optionally dependencies only for this prompt can be added with "if". If a prompt is not present, the config option is a non-visible symbol, meaning its value cannot be directly changed by the user (such as altering the value in ``.config``) and the option will not appear in any config menus. Its value can only be set via "default" and "select" (see below).”h]”(hX<Every menu entry can have at most one prompt, which is used to display to the user. Optionally dependencies only for this prompt can be added with “ifâ€�. If a prompt is not present, the config option is a non-visible symbol, meaning its value cannot be directly changed by the user (such as altering the value in ”…”�”}”(hjßh²hh³Nh´NubhŒliteral”“”)�”}”(hŒ ``.config``”h]”hŒ.config”…”�”}”(hjéh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jçhjßubhŒ) and the option will not appear in any config menus. Its value can only be set via “defaultâ€� and “selectâ€� (see below).”…”�”}”(hjßh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KGhjÍubeh}”(h]”h ]”h"]”h$]”h&]”uh1j{hjxh²hh³hÊh´Nubj|)�”}”(hX�default value: "default" ["if" ] A config option can have any number of default values. If multiple default values are visible, only the first defined one is active. Default values are not limited to the menu entry where they are defined. This means the default can be defined somewhere else or be overridden by an earlier definition. The default value is only assigned to the config symbol if no other value was set by the user (via the input prompt above). If an input prompt is visible the default value is presented to the user and can be overridden by him. Optionally, dependencies only for this default value can be added with "if". ”h]”(hÝ)�”}”(hŒ-default value: "default" ["if" ]”h]”hŒ5default value: “defaultâ€� [“ifâ€� ]”…”�”}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KOhjubhÝ)�”}”(hX]A config option can have any number of default values. If multiple default values are visible, only the first defined one is active. Default values are not limited to the menu entry where they are defined. This means the default can be defined somewhere else or be overridden by an earlier definition. The default value is only assigned to the config symbol if no other value was set by the user (via the input prompt above). If an input prompt is visible the default value is presented to the user and can be overridden by him. Optionally, dependencies only for this default value can be added with "if".”h]”hXaA config option can have any number of default values. If multiple default values are visible, only the first defined one is active. Default values are not limited to the menu entry where they are defined. This means the default can be defined somewhere else or be overridden by an earlier definition. The default value is only assigned to the config symbol if no other value was set by the user (via the input prompt above). If an input prompt is visible the default value is presented to the user and can be overridden by him. Optionally, dependencies only for this default value can be added with “ifâ€�.”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KQhjubeh}”(h]”h ]”h"]”h$]”h&]”uh1j{hjxh²hh³hÊh´Nubeh}”(h]”h ]”h"]”h$]”h&]”Œbullet”Œ-”uh1jvh³hÊh´K7hjWh²hubhŒ block_quote”“”)�”}”(hX€The default value deliberately defaults to 'n' in order to avoid bloating the build. With few exceptions, new config options should not change this. The intent is for "make oldconfig" to add as little as possible to the config from release to release. Note: Things that merit "default y/m" include: a) A new Kconfig option for something that used to always be built should be "default y". b) A new gatekeeping Kconfig option that hides/shows other Kconfig options (but does not generate any code of its own), should be "default y" so people will see those other options. c) Sub-driver behavior or similar options for a driver that is "default n". This allows you to provide sane defaults. d) Hardware or infrastructure that everybody expects, such as CONFIG_NET or CONFIG_BLOCK. These are rare exceptions. ”h]”(hÝ)�”}”(hŒûThe default value deliberately defaults to 'n' in order to avoid bloating the build. With few exceptions, new config options should not change this. The intent is for "make oldconfig" to add as little as possible to the config from release to release.”h]”hXThe default value deliberately defaults to ‘n’ in order to avoid bloating the build. With few exceptions, new config options should not change this. The intent is for “make oldconfigâ€� to add as little as possible to the config from release to release.”…”�”}”(hj;h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´K]hj7ubhŒdefinition_list”“”)�”}”(hhh]”hŒdefinition_list_item”“”)�”}”(hX=Note: Things that merit "default y/m" include: a) A new Kconfig option for something that used to always be built should be "default y". b) A new gatekeeping Kconfig option that hides/shows other Kconfig options (but does not generate any code of its own), should be "default y" so people will see those other options. c) Sub-driver behavior or similar options for a driver that is "default n". This allows you to provide sane defaults. d) Hardware or infrastructure that everybody expects, such as CONFIG_NET or CONFIG_BLOCK. These are rare exceptions. ”h]”(hŒterm”“”)�”}”(hŒNote:”h]”hŒNote:”…”�”}”(hjVh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jTh³hÊh´KphjPubhŒ definition”“”)�”}”(hhh]”(hÝ)�”}”(hŒ(Things that merit "default y/m" include:”h]”hŒ,Things that merit “default y/mâ€� include:”…”�”}”(hjih²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KchjfubhŒenumerated_list”“”)�”}”(hhh]”(j|)�”}”(hŒWA new Kconfig option for something that used to always be built should be "default y". ”h]”hÝ)�”}”(hŒVA new Kconfig option for something that used to always be built should be "default y".”h]”hŒZA new Kconfig option for something that used to always be built should be “default yâ€�.”…”�”}”(hj€h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Kehj|ubah}”(h]”h ]”h"]”h$]”h&]”uh1j{hjyubj|)�”}”(hŒ³A new gatekeeping Kconfig option that hides/shows other Kconfig options (but does not generate any code of its own), should be "default y" so people will see those other options. ”h]”hÝ)�”}”(hŒ²A new gatekeeping Kconfig option that hides/shows other Kconfig options (but does not generate any code of its own), should be "default y" so people will see those other options.”h]”hŒ¶A new gatekeeping Kconfig option that hides/shows other Kconfig options (but does not generate any code of its own), should be “default yâ€� so people will see those other options.”…”�”}”(hj˜h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Khhj”ubah}”(h]”h ]”h"]”h$]”h&]”uh1j{hjyubj|)�”}”(hŒsSub-driver behavior or similar options for a driver that is "default n". This allows you to provide sane defaults. ”h]”hÝ)�”}”(hŒrSub-driver behavior or similar options for a driver that is "default n". This allows you to provide sane defaults.”h]”hŒvSub-driver behavior or similar options for a driver that is “default nâ€�. This allows you to provide sane defaults.”…”�”}”(hj°h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Klhj¬ubah}”(h]”h ]”h"]”h$]”h&]”uh1j{hjyubj|)�”}”(hŒrHardware or infrastructure that everybody expects, such as CONFIG_NET or CONFIG_BLOCK. These are rare exceptions. ”h]”hÝ)�”}”(hŒqHardware or infrastructure that everybody expects, such as CONFIG_NET or CONFIG_BLOCK. These are rare exceptions.”h]”hŒqHardware or infrastructure that everybody expects, such as CONFIG_NET or CONFIG_BLOCK. These are rare exceptions.”…”�”}”(hjÈh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KohjÄubah}”(h]”h ]”h"]”h$]”h&]”uh1j{hjyubeh}”(h]”h ]”h"]”h$]”h&]”Œenumtype”Œ loweralpha”Œprefix”hŒsuffix”Œ)”uh1jwhjfubeh}”(h]”h ]”h"]”h$]”h&]”uh1jdhjPubeh}”(h]”h ]”h"]”h$]”h&]”uh1jNh³hÊh´KphjKubah}”(h]”h ]”h"]”h$]”h&]”uh1jIhj7ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j5h³hÊh´K]hjWh²hubjw)�”}”(hhh]”(j|)�”}”(hŒátype definition + default value:: "def_bool"/"def_tristate" ["if" ] This is a shorthand notation for a type definition plus a value. Optionally dependencies for this default value can be added with "if". ”h]”(hÝ)�”}”(hŒ!type definition + default value::”h]”hŒ type definition + default value:”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Krhjubhí)�”}”(hŒ."def_bool"/"def_tristate" ["if" ]”h]”hŒ."def_bool"/"def_tristate" ["if" ]”…”�”}”hjsbah}”(h]”h ]”h"]”h$]”h&]”hühýuh1hìh³hÊh´KthjubhÝ)�”}”(hŒ‡This is a shorthand notation for a type definition plus a value. Optionally dependencies for this default value can be added with "if".”h]”hŒ‹This is a shorthand notation for a type definition plus a value. Optionally dependencies for this default value can be added with “ifâ€�.”…”�”}”(hj"h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Kvhjubeh}”(h]”h ]”h"]”h$]”h&]”uh1j{hjÿh²hh³hÊh´Nubj|)�”}”(hX�dependencies: "depends on" ["if" ] This defines a dependency for this menu entry. If multiple dependencies are defined, they are connected with '&&'. Dependencies are applied to all other options within this menu entry (which also accept an "if" expression), so these two examples are equivalent:: bool "foo" if BAR default y if BAR and:: depends on BAR bool "foo" default y The dependency definition itself may be conditional by appending "if" followed by an expression. For example:: config FOO tristate depends on BAR if BAZ meaning that FOO is constrained by the value of BAR only if BAZ is also set. ”h]”(hÝ)�”}”(hŒ/dependencies: "depends on" ["if" ]”h]”hŒ7dependencies: “depends onâ€� [“ifâ€� ]”…”�”}”(hj:h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Kyhj6ubhÝ)�”}”(hXThis defines a dependency for this menu entry. If multiple dependencies are defined, they are connected with '&&'. Dependencies are applied to all other options within this menu entry (which also accept an "if" expression), so these two examples are equivalent::”h]”hX This defines a dependency for this menu entry. If multiple dependencies are defined, they are connected with ‘&&’. Dependencies are applied to all other options within this menu entry (which also accept an “ifâ€� expression), so these two examples are equivalent:”…”�”}”(hjHh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´K{hj6ubhí)�”}”(hŒ"bool "foo" if BAR default y if BAR”h]”hŒ"bool "foo" if BAR default y if BAR”…”�”}”hjVsbah}”(h]”h ]”h"]”h$]”h&]”hühýuh1hìh³hÊh´K€hj6ubhÝ)�”}”(hŒand::”h]”hŒand:”…”�”}”(hjdh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Kƒhj6ubhí)�”}”(hŒ#depends on BAR bool "foo" default y”h]”hŒ#depends on BAR bool "foo" default y”…”�”}”hjrsbah}”(h]”h ]”h"]”h$]”h&]”hühýuh1hìh³hÊh´K…hj6ubhÝ)�”}”(hŒnThe dependency definition itself may be conditional by appending "if" followed by an expression. For example::”h]”hŒqThe dependency definition itself may be conditional by appending “ifâ€� followed by an expression. For example:”…”�”}”(hj€h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´K‰hj6ubhí)�”}”(hŒ1config FOO tristate depends on BAR if BAZ”h]”hŒ1config FOO tristate depends on BAR if BAZ”…”�”}”hjŽsbah}”(h]”h ]”h"]”h$]”h&]”hühýuh1hìh³hÊh´KŒhj6ubhÝ)�”}”(hŒLmeaning that FOO is constrained by the value of BAR only if BAZ is also set.”h]”hŒLmeaning that FOO is constrained by the value of BAR only if BAZ is also set.”…”�”}”(hjœh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´K�hj6ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j{hjÿh²hh³hÊh´Nubj|)�”}”(hXóreverse dependencies: "select" ["if" ] While normal dependencies reduce the upper limit of a symbol (see below), reverse dependencies can be used to force a lower limit of another symbol. The value of the current menu symbol is used as the minimal value can be set to. If is selected multiple times, the limit is set to the largest selection. Reverse dependencies can only be used with boolean or tristate symbols. Note: select should be used with care. select will force a symbol to a value without visiting the dependencies. By abusing select you are able to select a symbol FOO even if FOO depends on BAR that is not set. In general use select only for non-visible symbols (no prompts anywhere) and for symbols with no dependencies. That will limit the usefulness but on the other hand avoid the illegal configurations all over. If "select" is followed by "if" , will be selected by the logical AND of the value of the current menu symbol and . This means, the lower limit can be downgraded due to the presence of "if" . This behavior may seem weird, but we rely on it. (The future of this behavior is undecided.) ”h]”(hÝ)�”}”(hŒ5reverse dependencies: "select" ["if" ]”h]”hŒ=reverse dependencies: “selectâ€� [“ifâ€� ]”…”�”}”(hj´h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´K“hj°ubhÝ)�”}”(hX‰While normal dependencies reduce the upper limit of a symbol (see below), reverse dependencies can be used to force a lower limit of another symbol. The value of the current menu symbol is used as the minimal value can be set to. If is selected multiple times, the limit is set to the largest selection. Reverse dependencies can only be used with boolean or tristate symbols.”h]”hX‰While normal dependencies reduce the upper limit of a symbol (see below), reverse dependencies can be used to force a lower limit of another symbol. The value of the current menu symbol is used as the minimal value can be set to. If is selected multiple times, the limit is set to the largest selection. Reverse dependencies can only be used with boolean or tristate symbols.”…”�”}”(hjÂh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´K•hj°ubjJ)�”}”(hhh]”jO)�”}”(hXãNote: select should be used with care. select will force a symbol to a value without visiting the dependencies. By abusing select you are able to select a symbol FOO even if FOO depends on BAR that is not set. In general use select only for non-visible symbols (no prompts anywhere) and for symbols with no dependencies. That will limit the usefulness but on the other hand avoid the illegal configurations all over. If "select" is followed by "if" , will be selected by the logical AND of the value of the current menu symbol and . This means, the lower limit can be downgraded due to the presence of "if" . This behavior may seem weird, but we rely on it. (The future of this behavior is undecided.) ”h]”(jU)�”}”(hŒNote:”h]”hŒNote:”…”�”}”(hj×h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jTh³hÊh´K«hjÓubje)�”}”(hhh]”(hÝ)�”}”(hXšselect should be used with care. select will force a symbol to a value without visiting the dependencies. By abusing select you are able to select a symbol FOO even if FOO depends on BAR that is not set. In general use select only for non-visible symbols (no prompts anywhere) and for symbols with no dependencies. That will limit the usefulness but on the other hand avoid the illegal configurations all over.”h]”hXšselect should be used with care. select will force a symbol to a value without visiting the dependencies. By abusing select you are able to select a symbol FOO even if FOO depends on BAR that is not set. In general use select only for non-visible symbols (no prompts anywhere) and for symbols with no dependencies. That will limit the usefulness but on the other hand avoid the illegal configurations all over.”…”�”}”(hjèh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KžhjåubhÝ)�”}”(hX@If "select" is followed by "if" , will be selected by the logical AND of the value of the current menu symbol and . This means, the lower limit can be downgraded due to the presence of "if" . This behavior may seem weird, but we rely on it. (The future of this behavior is undecided.)”h]”hXLIf “selectâ€� is followed by “ifâ€� , will be selected by the logical AND of the value of the current menu symbol and . This means, the lower limit can be downgraded due to the presence of “ifâ€� . This behavior may seem weird, but we rely on it. (The future of this behavior is undecided.)”…”�”}”(hjöh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´K§hjåubeh}”(h]”h ]”h"]”h$]”h&]”uh1jdhjÓubeh}”(h]”h ]”h"]”h$]”h&]”uh1jNh³hÊh´K«hjÐubah}”(h]”h ]”h"]”h$]”h&]”uh1jIhj°ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j{hjÿh²hh³Nh´Nubj|)�”}”(hXµweak reverse dependencies: "imply" ["if" ] This is similar to "select" as it enforces a lower limit on another symbol except that the "implied" symbol's value may still be set to n from a direct dependency or with a visible prompt. Given the following example:: config FOO tristate "foo" imply BAZ config BAZ tristate "baz" depends on BAR The following values are possible: === === ============= ============== FOO BAR BAZ's default choice for BAZ === === ============= ============== n y n N/m/y m y m M/y/n y y y Y/m/n n m n N/m m m m M/n y m m M/n y n * N === === ============= ============== This is useful e.g. with multiple drivers that want to indicate their ability to hook into a secondary subsystem while allowing the user to configure that subsystem out without also having to unset these drivers. Note: If the feature provided by BAZ is highly desirable for FOO, FOO should imply not only BAZ, but also its dependency BAR:: config FOO tristate "foo" imply BAR imply BAZ Note: If "imply" is followed by "if" , the default of will be the logical AND of the value of the current menu symbol and . (The future of this behavior is undecided.) ”h]”(hÝ)�”}”(hŒ9weak reverse dependencies: "imply" ["if" ]”h]”hŒAweak reverse dependencies: “implyâ€� [“ifâ€� ]”…”�”}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´K­hjubhÝ)�”}”(hŒ¼This is similar to "select" as it enforces a lower limit on another symbol except that the "implied" symbol's value may still be set to n from a direct dependency or with a visible prompt.”h]”hŒÆThis is similar to “selectâ€� as it enforces a lower limit on another symbol except that the “impliedâ€� symbol’s value may still be set to n from a direct dependency or with a visible prompt.”…”�”}”(hj.h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´K¯hjubhÝ)�”}”(hŒGiven the following example::”h]”hŒGiven the following example:”…”�”}”(hj<h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´K³hjubhí)�”}”(hŒ]config FOO tristate "foo" imply BAZ config BAZ tristate "baz" depends on BAR”h]”hŒ]config FOO tristate "foo" imply BAZ config BAZ tristate "baz" depends on BAR”…”�”}”hjJsbah}”(h]”h ]”h"]”h$]”h&]”hühýuh1hìh³hÊh´KµhjubhÝ)�”}”(hŒ"The following values are possible:”h]”hŒ"The following values are possible:”…”�”}”(hjXh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´K½hjubj6)�”}”(hXl=== === ============= ============== FOO BAR BAZ's default choice for BAZ === === ============= ============== n y n N/m/y m y m M/y/n y y y Y/m/n n m n N/m m m m M/n y m m M/n y n * N === === ============= ============== ”h]”hŒtable”“”)�”}”(hhh]”hŒtgroup”“”)�”}”(hhh]”(hŒcolspec”“”)�”}”(hhh]”h}”(h]”h ]”h"]”h$]”h&]”Œcolwidth”Kuh1jthjqubju)�”}”(hhh]”h}”(h]”h ]”h"]”h$]”h&]”Œcolwidth”Kuh1jthjqubju)�”}”(hhh]”h}”(h]”h ]”h"]”h$]”h&]”Œcolwidth”K uh1jthjqubju)�”}”(hhh]”h}”(h]”h ]”h"]”h$]”h&]”Œcolwidth”Kuh1jthjqubhŒthead”“”)�”}”(hhh]”hŒrow”“”)�”}”(hhh]”(hŒentry”“”)�”}”(hhh]”hÝ)�”}”(hŒFOO”h]”hŒFOO”…”�”}”(hj­h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KÀhjªubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hj¥ubj©)�”}”(hhh]”hÝ)�”}”(hŒBAR”h]”hŒBAR”…”�”}”(hjÄh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KÀhjÁubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hj¥ubj©)�”}”(hhh]”hÝ)�”}”(hŒ BAZ's default”h]”hŒBAZ’s default”…”�”}”(hjÛh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KÀhjØubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hj¥ubj©)�”}”(hhh]”hÝ)�”}”(hŒchoice for BAZ”h]”hŒchoice for BAZ”…”�”}”(hjòh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KÀhjïubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hj¥ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j£hj ubah}”(h]”h ]”h"]”h$]”h&]”uh1jžhjqubhŒtbody”“”)�”}”(hhh]”(j¤)�”}”(hhh]”(j©)�”}”(hhh]”hÝ)�”}”(hŒn”h]”hŒn”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KÂhjubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hjubj©)�”}”(hhh]”hÝ)�”}”(hŒy”h]”hŒy”…”�”}”(hj4h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KÂhj1ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hjubj©)�”}”(hhh]”hÝ)�”}”(hjh]”hŒn”…”�”}”(hjKh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KÂhjHubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hjubj©)�”}”(hhh]”hÝ)�”}”(hŒN/m/y”h]”hŒN/m/y”…”�”}”(hjah²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KÂhj^ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hjubeh}”(h]”h ]”h"]”h$]”h&]”uh1j£hjubj¤)�”}”(hhh]”(j©)�”}”(hhh]”hÝ)�”}”(hŒm”h]”hŒm”…”�”}”(hj�h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KÃhj~ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hj{ubj©)�”}”(hhh]”hÝ)�”}”(hj6h]”hŒy”…”�”}”(hj˜h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KÃhj•ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hj{ubj©)�”}”(hhh]”hÝ)�”}”(hjƒh]”hŒm”…”�”}”(hj®h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KÃhj«ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hj{ubj©)�”}”(hhh]”hÝ)�”}”(hŒM/y/n”h]”hŒM/y/n”…”�”}”(hjÄh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KÃhjÁubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hj{ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j£hjubj¤)�”}”(hhh]”(j©)�”}”(hhh]”hÝ)�”}”(hj6h]”hŒy”…”�”}”(hjäh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KÄhjáubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hjÞubj©)�”}”(hhh]”hÝ)�”}”(hj6h]”hŒy”…”�”}”(hjúh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KÄhj÷ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hjÞubj©)�”}”(hhh]”hÝ)�”}”(hj6h]”hŒy”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KÄhj ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hjÞubj©)�”}”(hhh]”hÝ)�”}”(hŒY/m/n”h]”hŒY/m/n”…”�”}”(hj&h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KÄhj#ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hjÞubeh}”(h]”h ]”h"]”h$]”h&]”uh1j£hjubj¤)�”}”(hhh]”(j©)�”}”(hhh]”hÝ)�”}”(hjh]”hŒn”…”�”}”(hjFh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KÅhjCubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hj@ubj©)�”}”(hhh]”hÝ)�”}”(hjƒh]”hŒm”…”�”}”(hj\h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KÅhjYubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hj@ubj©)�”}”(hhh]”hÝ)�”}”(hjh]”hŒn”…”�”}”(hjrh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KÅhjoubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hj@ubj©)�”}”(hhh]”hÝ)�”}”(hŒN/m”h]”hŒN/m”…”�”}”(hjˆh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KÅhj…ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hj@ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j£hjubj¤)�”}”(hhh]”(j©)�”}”(hhh]”hÝ)�”}”(hjƒh]”hŒm”…”�”}”(hj¨h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KÆhj¥ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hj¢ubj©)�”}”(hhh]”hÝ)�”}”(hjƒh]”hŒm”…”�”}”(hj¾h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KÆhj»ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hj¢ubj©)�”}”(hhh]”hÝ)�”}”(hjƒh]”hŒm”…”�”}”(hjÔh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KÆhjÑubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hj¢ubj©)�”}”(hhh]”hÝ)�”}”(hŒM/n”h]”hŒM/n”…”�”}”(hjêh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KÆhjçubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hj¢ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j£hjubj¤)�”}”(hhh]”(j©)�”}”(hhh]”hÝ)�”}”(hj6h]”hŒy”…”�”}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KÇhjubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hjubj©)�”}”(hhh]”hÝ)�”}”(hjƒh]”hŒm”…”�”}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KÇhjubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hjubj©)�”}”(hhh]”hÝ)�”}”(hjƒh]”hŒm”…”�”}”(hj6h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KÇhj3ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hjubj©)�”}”(hhh]”hÝ)�”}”(hŒM/n”h]”hŒM/n”…”�”}”(hjLh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KÇhjIubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hjubeh}”(h]”h ]”h"]”h$]”h&]”uh1j£hjubj¤)�”}”(hhh]”(j©)�”}”(hhh]”hÝ)�”}”(hj6h]”hŒy”…”�”}”(hjlh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KÈhjiubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hjfubj©)�”}”(hhh]”hÝ)�”}”(hjh]”hŒn”…”�”}”(hj‚h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KÈhjubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hjfubj©)�”}”(hhh]”jw)�”}”(hhh]”j|)�”}”(hhh]”h}”(h]”h ]”h"]”h$]”h&]”uh1j{hj˜ubah}”(h]”h ]”h"]”h$]”h&]”j3Œ*”uh1jvh³hÊh´KÈhj•ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hjfubj©)�”}”(hhh]”hÝ)�”}”(hŒN”h]”hŒN”…”�”}”(hj´h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KÈhj±ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hjfubeh}”(h]”h ]”h"]”h$]”h&]”uh1j£hjubeh}”(h]”h ]”h"]”h$]”h&]”uh1jhjqubeh}”(h]”h ]”h"]”h$]”h&]”Œcols”Kuh1johjlubah}”(h]”h ]”h"]”h$]”h&]”uh1jjhjfubah}”(h]”h ]”h"]”h$]”h&]”uh1j5h³hÊh´K¿hjubhÝ)�”}”(hŒÔThis is useful e.g. with multiple drivers that want to indicate their ability to hook into a secondary subsystem while allowing the user to configure that subsystem out without also having to unset these drivers.”h]”hŒÔThis is useful e.g. with multiple drivers that want to indicate their ability to hook into a secondary subsystem while allowing the user to configure that subsystem out without also having to unset these drivers.”…”�”}”(hjçh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KËhjubhÝ)�”}”(hŒ~Note: If the feature provided by BAZ is highly desirable for FOO, FOO should imply not only BAZ, but also its dependency BAR::”h]”hŒ}Note: If the feature provided by BAZ is highly desirable for FOO, FOO should imply not only BAZ, but also its dependency BAR:”…”�”}”(hjõh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KÏhjubhí)�”}”(hŒ9config FOO tristate "foo" imply BAR imply BAZ”h]”hŒ9config FOO tristate "foo" imply BAR imply BAZ”…”�”}”hjsbah}”(h]”h ]”h"]”h$]”h&]”hühýuh1hìh³hÊh´KÒhjubhÝ)�”}”(hŒÅNote: If "imply" is followed by "if" , the default of will be the logical AND of the value of the current menu symbol and . (The future of this behavior is undecided.)”h]”hŒÍNote: If “implyâ€� is followed by “ifâ€� , the default of will be the logical AND of the value of the current menu symbol and . (The future of this behavior is undecided.)”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´K×hjubeh}”(h]”h ]”h"]”h$]”h&]”uh1j{hjÿh²hh³hÊh´Nubj|)�”}”(hXflimiting menu display: "visible if" This attribute is only applicable to menu blocks, if the condition is false, the menu block is not displayed to the user (the symbols contained there can still be selected by other symbols, though). It is similar to a conditional "prompt" attribute for individual menu entries. Default value of "visible" is true. ”h]”(hÝ)�”}”(hŒ*limiting menu display: "visible if" ”h]”hŒ.limiting menu display: “visible ifâ€� ”…”�”}”(hj)h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KÛhj%ubhÝ)�”}”(hX9This attribute is only applicable to menu blocks, if the condition is false, the menu block is not displayed to the user (the symbols contained there can still be selected by other symbols, though). It is similar to a conditional "prompt" attribute for individual menu entries. Default value of "visible" is true.”h]”hXAThis attribute is only applicable to menu blocks, if the condition is false, the menu block is not displayed to the user (the symbols contained there can still be selected by other symbols, though). It is similar to a conditional “promptâ€� attribute for individual menu entries. Default value of “visibleâ€� is true.”…”�”}”(hj7h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KÝhj%ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j{hjÿh²hh³hÊh´Nubj|)�”}”(hXnumerical ranges: "range" ["if" ] This allows limiting the range of possible input values for int and hex symbols. The user can only input a value which is larger than or equal to the first symbol and smaller than or equal to the second symbol. ”h]”(hÝ)�”}”(hŒ9numerical ranges: "range" ["if" ]”h]”hŒAnumerical ranges: “rangeâ€� [“ifâ€� ]”…”�”}”(hjOh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KãhjKubhÝ)�”}”(hŒÒThis allows limiting the range of possible input values for int and hex symbols. The user can only input a value which is larger than or equal to the first symbol and smaller than or equal to the second symbol.”h]”hŒÒThis allows limiting the range of possible input values for int and hex symbols. The user can only input a value which is larger than or equal to the first symbol and smaller than or equal to the second symbol.”…”�”}”(hj]h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KåhjKubeh}”(h]”h ]”h"]”h$]”h&]”uh1j{hjÿh²hh³hÊh´Nubj|)�”}”(hŒÙhelp text: "help" This defines a help text. The end of the help text is determined by the indentation level, this means it ends at the first line which has a smaller indentation than the first line of the help text. ”h]”(hÝ)�”}”(hŒhelp text: "help"”h]”hŒhelp text: “helpâ€�”…”�”}”(hjuh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´KêhjqubhÝ)�”}”(hŒÅThis defines a help text. The end of the help text is determined by the indentation level, this means it ends at the first line which has a smaller indentation than the first line of the help text.”h]”hŒÅThis defines a help text. The end of the help text is determined by the indentation level, this means it ends at the first line which has a smaller indentation than the first line of the help text.”…”�”}”(hjƒh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Kìhjqubeh}”(h]”h ]”h"]”h$]”h&]”uh1j{hjÿh²hh³hÊh´Nubj|)�”}”(hŒËmodule attribute: "modules" This declares the symbol to be used as the MODULES symbol, which enables the third modular state for all config symbols. At most one symbol may have the "modules" option set. ”h]”hÝ)�”}”(hŒÊmodule attribute: "modules" This declares the symbol to be used as the MODULES symbol, which enables the third modular state for all config symbols. At most one symbol may have the "modules" option set.”h]”hŒÒmodule attribute: “modulesâ€� This declares the symbol to be used as the MODULES symbol, which enables the third modular state for all config symbols. At most one symbol may have the “modulesâ€� option set.”…”�”}”(hj›h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Kðhj—ubah}”(h]”h ]”h"]”h$]”h&]”uh1j{hjÿh²hh³hÊh´Nubj|)�”}”(hX¯transitional attribute: "transitional" This declares the symbol as transitional, meaning it should be processed during configuration but omitted from newly written .config files. Transitional symbols are useful for backward compatibility during config option migrations - they allow olddefconfig to process existing .config files while ensuring the old option doesn't appear in new configurations. A transitional symbol: - Has no prompt (is not visible to users in menus) - Is processed normally during configuration (values are read and used) - Can be referenced in default expressions of other symbols - Is not written to new .config files - Cannot have any other properties (it is a pass-through option) Example migration from OLD_NAME to NEW_NAME:: config NEW_NAME bool "New option name" default OLD_NAME help This replaces the old CONFIG_OLD_NAME option. config OLD_NAME bool transitional help Transitional config for OLD_NAME to NEW_NAME migration. With this setup, existing .config files with "CONFIG_OLD_NAME=y" will result in "CONFIG_NEW_NAME=y" being set, while CONFIG_OLD_NAME will be omitted from newly written .config files. ”h]”(hÝ)�”}”(hX�transitional attribute: "transitional" This declares the symbol as transitional, meaning it should be processed during configuration but omitted from newly written .config files. Transitional symbols are useful for backward compatibility during config option migrations - they allow olddefconfig to process existing .config files while ensuring the old option doesn't appear in new configurations.”h]”hX“transitional attribute: “transitionalâ€� This declares the symbol as transitional, meaning it should be processed during configuration but omitted from newly written .config files. Transitional symbols are useful for backward compatibility during config option migrations - they allow olddefconfig to process existing .config files while ensuring the old option doesn’t appear in new configurations.”…”�”}”(hj³h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Kõhj¯ubhÝ)�”}”(hX4A transitional symbol: - Has no prompt (is not visible to users in menus) - Is processed normally during configuration (values are read and used) - Can be referenced in default expressions of other symbols - Is not written to new .config files - Cannot have any other properties (it is a pass-through option)”h]”hX4A transitional symbol: - Has no prompt (is not visible to users in menus) - Is processed normally during configuration (values are read and used) - Can be referenced in default expressions of other symbols - Is not written to new .config files - Cannot have any other properties (it is a pass-through option)”…”�”}”(hjÁh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Kühj¯ubhÝ)�”}”(hŒ-Example migration from OLD_NAME to NEW_NAME::”h]”hŒ,Example migration from OLD_NAME to NEW_NAME:”…”�”}”(hjÏh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Mhj¯ubhí)�”}”(hŒîconfig NEW_NAME bool "New option name" default OLD_NAME help This replaces the old CONFIG_OLD_NAME option. config OLD_NAME bool transitional help Transitional config for OLD_NAME to NEW_NAME migration.”h]”hŒîconfig NEW_NAME bool "New option name" default OLD_NAME help This replaces the old CONFIG_OLD_NAME option. config OLD_NAME bool transitional help Transitional config for OLD_NAME to NEW_NAME migration.”…”�”}”hjÝsbah}”(h]”h ]”h"]”h$]”h&]”hühýuh1hìh³hÊh´Mhj¯ubhÝ)�”}”(hŒ¶With this setup, existing .config files with "CONFIG_OLD_NAME=y" will result in "CONFIG_NEW_NAME=y" being set, while CONFIG_OLD_NAME will be omitted from newly written .config files.”h]”hŒ¾With this setup, existing .config files with “CONFIG_OLD_NAME=yâ€� will result in “CONFIG_NEW_NAME=yâ€� being set, while CONFIG_OLD_NAME will be omitted from newly written .config files.”…”�”}”(hjëh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Mhj¯ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j{hjÿh²hh³hÊh´Nubeh}”(h]”h ]”h"]”h$]”h&]”j3j4uh1jvh³hÊh´KrhjWh²hubeh}”(h]”Œmenu-attributes”ah ]”h"]”Œmenu attributes”ah$]”h&]”uh1hµhh·h²hh³hÊh´K2ubh¶)�”}”(hhh]”(h»)�”}”(hŒMenu dependencies”h]”hŒMenu dependencies”…”�”}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj h²hh³hÊh´MubhÝ)�”}”(hXDependencies define the visibility of a menu entry and can also reduce the input range of tristate symbols. The tristate logic used in the expressions uses one more state than normal boolean logic to express the module state. Dependency expressions have the following syntax::”h]”hXDependencies define the visibility of a menu entry and can also reduce the input range of tristate symbols. The tristate logic used in the expressions uses one more state than normal boolean logic to express the module state. Dependency expressions have the following syntax:”…”�”}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Mhj h²hubhí)�”}”(hX% ::= (1) '=' (2) '!=' (3) '<' (4) '>' (4) '<=' (4) '>=' (4) '(' ')' (5) '!' (6) '&&' (7) '||' (8)”h]”hX% ::= (1) '=' (2) '!=' (3) '<' (4) '>' (4) '<=' (4) '>=' (4) '(' ')' (5) '!' (6) '&&' (7) '||' (8)”…”�”}”hj, sbah}”(h]”h ]”h"]”h$]”h&]”hühýuh1hìh³hÊh´Mhj h²hubhÝ)�”}”(hŒ9Expressions are listed in decreasing order of precedence.”h]”hŒ9Expressions are listed in decreasing order of precedence.”…”�”}”(hj: h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M)hj h²hubjx)�”}”(hhh]”(j|)�”}”(hŒ¥Convert the symbol into an expression. Boolean and tristate symbols are simply converted into the respective expression values. All other symbol types result in 'n'.”h]”hÝ)�”}”(hŒ¥Convert the symbol into an expression. Boolean and tristate symbols are simply converted into the respective expression values. All other symbol types result in 'n'.”h]”hŒ©Convert the symbol into an expression. Boolean and tristate symbols are simply converted into the respective expression values. All other symbol types result in ‘n’.”…”�”}”(hjO h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M+hjK ubah}”(h]”h ]”h"]”h$]”h&]”uh1j{hjH h²hh³hÊh´Nubj|)�”}”(hŒGIf the values of both symbols are equal, it returns 'y', otherwise 'n'.”h]”hÝ)�”}”(hŒGIf the values of both symbols are equal, it returns 'y', otherwise 'n'.”h]”hŒOIf the values of both symbols are equal, it returns ‘y’, otherwise ‘n’.”…”�”}”(hjg h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M.hjc ubah}”(h]”h ]”h"]”h$]”h&]”uh1j{hjH h²hh³hÊh´Nubj|)�”}”(hŒGIf the values of both symbols are equal, it returns 'n', otherwise 'y'.”h]”hÝ)�”}”(hŒGIf the values of both symbols are equal, it returns 'n', otherwise 'y'.”h]”hŒOIf the values of both symbols are equal, it returns ‘n’, otherwise ‘y’.”…”�”}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M0hj{ ubah}”(h]”h ]”h"]”h$]”h&]”uh1j{hjH h²hh³hÊh´Nubj|)�”}”(hŒ‘If value of is respectively lower, greater, lower-or-equal, or greater-or-equal than value of , it returns 'y', otherwise 'n'.”h]”hÝ)�”}”(hŒ‘If value of is respectively lower, greater, lower-or-equal, or greater-or-equal than value of , it returns 'y', otherwise 'n'.”h]”hŒ™If value of is respectively lower, greater, lower-or-equal, or greater-or-equal than value of , it returns ‘y’, otherwise ‘n’.”…”�”}”(hj— h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M2hj“ ubah}”(h]”h ]”h"]”h$]”h&]”uh1j{hjH h²hh³hÊh´Nubj|)�”}”(hŒAReturns the value of the expression. Used to override precedence.”h]”hÝ)�”}”(hj­ h]”hŒAReturns the value of the expression. Used to override precedence.”…”�”}”(hj¯ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M5hj« ubah}”(h]”h ]”h"]”h$]”h&]”uh1j{hjH h²hh³hÊh´Nubj|)�”}”(hŒ!Returns the result of (2-/expr/).”h]”hÝ)�”}”(hjÄ h]”hŒ!Returns the result of (2-/expr/).”…”�”}”(hjÆ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M6hj ubah}”(h]”h ]”h"]”h$]”h&]”uh1j{hjH h²hh³hÊh´Nubj|)�”}”(hŒ*Returns the result of min(/expr/, /expr/).”h]”hÝ)�”}”(hjÛ h]”hŒ*Returns the result of min(/expr/, /expr/).”…”�”}”(hjÝ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M7hjÙ ubah}”(h]”h ]”h"]”h$]”h&]”uh1j{hjH h²hh³hÊh´Nubj|)�”}”(hŒ+Returns the result of max(/expr/, /expr/). ”h]”hÝ)�”}”(hŒ*Returns the result of max(/expr/, /expr/).”h]”hŒ*Returns the result of max(/expr/, /expr/).”…”�”}”(hjô h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M8hjð ubah}”(h]”h ]”h"]”h$]”h&]”uh1j{hjH h²hh³hÊh´Nubeh}”(h]”h ]”h"]”h$]”h&]”jâŒarabic”jäŒ(”jåjæuh1jwhj h²hh³hÊh´M+ubhÝ)�”}”(hŒ§An expression can have a value of 'n', 'm' or 'y' (or 0, 1, 2 respectively for calculations). A menu entry becomes visible when its expression evaluates to 'm' or 'y'.”h]”hŒ»An expression can have a value of ‘n’, ‘m’ or ‘y’ (or 0, 1, 2 respectively for calculations). A menu entry becomes visible when its expression evaluates to ‘m’ or ‘y’.”…”�”}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M:hj h²hubhÝ)�”}”(hXºThere are two types of symbols: constant and non-constant symbols. Non-constant symbols are the most common ones and are defined with the 'config' statement. Non-constant symbols consist entirely of alphanumeric characters or underscores. Constant symbols are only part of expressions. Constant symbols are always surrounded by single or double quotes. Within the quote, any other character is allowed and the quotes can be escaped using '\'.”h]”hXÀThere are two types of symbols: constant and non-constant symbols. Non-constant symbols are the most common ones and are defined with the ‘config’ statement. Non-constant symbols consist entirely of alphanumeric characters or underscores. Constant symbols are only part of expressions. Constant symbols are always surrounded by single or double quotes. Within the quote, any other character is allowed and the quotes can be escaped using ‘'.”…”�”}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M>hj h²hubeh}”(h]”Œmenu-dependencies”ah ]”h"]”Œmenu dependencies”ah$]”h&]”uh1hµhh·h²hh³hÊh´Mubh¶)�”}”(hhh]”(h»)�”}”(hŒMenu structure”h]”hŒMenu structure”…”�”}”(hj7 h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj4 h²hh³hÊh´MGubhÝ)�”}”(hŒjThe position of a menu entry in the tree is determined in two ways. First it can be specified explicitly::”h]”hŒiThe position of a menu entry in the tree is determined in two ways. First it can be specified explicitly:”…”�”}”(hjE h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MIhj4 h²hubhí)�”}”(hŒXmenu "Network device support" depends on NET config NETDEVICES ... endmenu”h]”hŒXmenu "Network device support" depends on NET config NETDEVICES ... endmenu”…”�”}”hjS sbah}”(h]”h ]”h"]”h$]”h&]”hühýuh1hìh³hÊh´MLhj4 h²hubhÝ)�”}”(hXAll entries within the "menu" ... "endmenu" block become a submenu of "Network device support". All subentries inherit the dependencies from the menu entry, e.g. this means the dependency "NET" is added to the dependency list of the config option NETDEVICES.”h]”hXAll entries within the “menuâ€� ... “endmenuâ€� block become a submenu of “Network device supportâ€�. All subentries inherit the dependencies from the menu entry, e.g. this means the dependency “NETâ€� is added to the dependency list of the config option NETDEVICES.”…”�”}”(hja h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MThj4 h²hubhÝ)�”}”(hX%The other way to generate the menu structure is done by analyzing the dependencies. If a menu entry somehow depends on the previous entry, it can be made a submenu of it. First, the previous (parent) symbol must be part of the dependency list and then one of these two conditions must be true:”h]”hX%The other way to generate the menu structure is done by analyzing the dependencies. If a menu entry somehow depends on the previous entry, it can be made a submenu of it. First, the previous (parent) symbol must be part of the dependency list and then one of these two conditions must be true:”…”�”}”(hjo h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MYhj4 h²hubjw)�”}”(hhh]”(j|)�”}”(hŒBthe child entry must become invisible, if the parent is set to 'n'”h]”hÝ)�”}”(hj‚ h]”hŒFthe child entry must become invisible, if the parent is set to ‘n’”…”�”}”(hj„ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M_hj€ ubah}”(h]”h ]”h"]”h$]”h&]”uh1j{hj} h²hh³hÊh´Nubj|)�”}”(hX(the child entry must only be visible, if the parent is visible:: config MODULES bool "Enable loadable module support" config MODVERSIONS bool "Set version information on all module symbols" depends on MODULES comment "module support disabled" depends on !MODULES ”h]”(hÝ)�”}”(hŒ@the child entry must only be visible, if the parent is visible::”h]”hŒ?the child entry must only be visible, if the parent is visible:”…”�”}”(hj› h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M`hj— ubhí)�”}”(hŒ×config MODULES bool "Enable loadable module support" config MODVERSIONS bool "Set version information on all module symbols" depends on MODULES comment "module support disabled" depends on !MODULES”h]”hŒ×config MODULES bool "Enable loadable module support" config MODVERSIONS bool "Set version information on all module symbols" depends on MODULES comment "module support disabled" depends on !MODULES”…”�”}”hj© sbah}”(h]”h ]”h"]”h$]”h&]”hühýuh1hìh³hÊh´Mbhj— ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j{hj} h²hh³hÊh´Nubeh}”(h]”h ]”h"]”h$]”h&]”j3j4uh1jvh³hÊh´M_hj4 h²hubhÝ)�”}”(hŒ±MODVERSIONS directly depends on MODULES, this means it's only visible if MODULES is different from 'n'. The comment on the other hand is only visible when MODULES is set to 'n'.”h]”hŒ»MODVERSIONS directly depends on MODULES, this means it’s only visible if MODULES is different from ‘n’. The comment on the other hand is only visible when MODULES is set to ‘n’.”…”�”}”(hjà h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Mlhj4 h²hubeh}”(h]”Œmenu-structure”ah ]”h"]”Œmenu structure”ah$]”h&]”uh1hµhh·h²hh³hÊh´MGubh¶)�”}”(hhh]”(h»)�”}”(hŒKconfig syntax”h]”hŒKconfig syntax”…”�”}”(hjÜ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjÙ h²hh³hÊh´MrubhÝ)�”}”(hŒŸThe configuration file describes a series of menu entries, where every line starts with a keyword (except help texts). The following keywords end a menu entry:”h]”hŒŸThe configuration file describes a series of menu entries, where every line starts with a keyword (except help texts). The following keywords end a menu entry:”…”�”}”(hjê h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MthjÙ h²hubjw)�”}”(hhh]”(j|)�”}”(hŒconfig”h]”hÝ)�”}”(hjý h]”hŒconfig”…”�”}”(hjÿ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Mxhjû ubah}”(h]”h ]”h"]”h$]”h&]”uh1j{hjø h²hh³hÊh´Nubj|)�”}”(hŒ menuconfig”h]”hÝ)�”}”(hj h]”hŒ menuconfig”…”�”}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Myhj ubah}”(h]”h ]”h"]”h$]”h&]”uh1j{hjø h²hh³hÊh´Nubj|)�”}”(hŒchoice/endchoice”h]”hÝ)�”}”(hj+ h]”hŒchoice/endchoice”…”�”}”(hj- h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Mzhj) ubah}”(h]”h ]”h"]”h$]”h&]”uh1j{hjø h²hh³hÊh´Nubj|)�”}”(hŒcomment”h]”hÝ)�”}”(hjB h]”hŒcomment”…”�”}”(hjD h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M{hj@ ubah}”(h]”h ]”h"]”h$]”h&]”uh1j{hjø h²hh³hÊh´Nubj|)�”}”(hŒ menu/endmenu”h]”hÝ)�”}”(hjY h]”hŒ menu/endmenu”…”�”}”(hj[ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M|hjW ubah}”(h]”h ]”h"]”h$]”h&]”uh1j{hjø h²hh³hÊh´Nubj|)�”}”(hŒif/endif”h]”hÝ)�”}”(hjp h]”hŒif/endif”…”�”}”(hjr h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M}hjn ubah}”(h]”h ]”h"]”h$]”h&]”uh1j{hjø h²hh³hÊh´Nubj|)�”}”(hŒsource ”h]”hÝ)�”}”(hŒsource”h]”hŒsource”…”�”}”(hj‰ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M~hj… ubah}”(h]”h ]”h"]”h$]”h&]”uh1j{hjø h²hh³hÊh´Nubeh}”(h]”h ]”h"]”h$]”h&]”j3j4uh1jvh³hÊh´MxhjÙ h²hubhÝ)�”}”(hŒ9The first five also start the definition of a menu entry.”h]”hŒ9The first five also start the definition of a menu entry.”…”�”}”(hj£ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M€hjÙ h²hubhÝ)�”}”(hŒconfig::”h]”hŒconfig:”…”�”}”(hj± h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M‚hjÙ h²hubhí)�”}”(hŒ""config" ”h]”hŒ""config" ”…”�”}”hj¿ sbah}”(h]”h ]”h"]”h$]”h&]”hühýuh1hìh³hÊh´M„hjÙ h²hubhÝ)�”}”(hŒUThis defines a config symbol and accepts any of above attributes as options.”h]”hŒUThis defines a config symbol and accepts any of above attributes as options.”…”�”}”(hjÍ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M‡hjÙ h²hubhÝ)�”}”(hŒ menuconfig::”h]”hŒ menuconfig:”…”�”}”(hjÛ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MŠhjÙ h²hubhí)�”}”(hŒ&"menuconfig" ”h]”hŒ&"menuconfig" ”…”�”}”hjé sbah}”(h]”h ]”h"]”h$]”h&]”hühýuh1hìh³hÊh´MŒhjÙ h²hubhÝ)�”}”(hXžThis is similar to the simple config entry above, but it also gives a hint to front ends, that all suboptions should be displayed as a separate list of options. To make sure all the suboptions will really show up under the menuconfig entry and not outside of it, every item from the list must depend on the menuconfig symbol. In practice, this is achieved by using one of the next two constructs::”h]”hX�This is similar to the simple config entry above, but it also gives a hint to front ends, that all suboptions should be displayed as a separate list of options. To make sure all the suboptions will really show up under the menuconfig entry and not outside of it, every item from the list must depend on the menuconfig symbol. In practice, this is achieved by using one of the next two constructs:”…”�”}”(hj÷ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M�hjÙ h²hubhí)�”}”(hŒ�(1): menuconfig M if M config C1 config C2 endif (2): menuconfig M config C1 depends on M config C2 depends on M”h]”hŒ�(1): menuconfig M if M config C1 config C2 endif (2): menuconfig M config C1 depends on M config C2 depends on M”…”�”}”hj sbah}”(h]”h ]”h"]”h$]”h&]”hühýuh1hìh³hÊh´M–hjÙ h²hubhÝ)�”}”(hŒ¨In the following examples (3) and (4), C1 and C2 still have the M dependency, but will not appear under menuconfig M anymore, because of C0, which doesn't depend on M::”h]”hŒ©In the following examples (3) and (4), C1 and C2 still have the M dependency, but will not appear under menuconfig M anymore, because of C0, which doesn’t depend on M:”…”�”}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M¤hjÙ h²hubhí)�”}”(hŒ™(3): menuconfig M config C0 if M config C1 config C2 endif (4): menuconfig M config C0 config C1 depends on M config C2 depends on M”h]”hŒ™(3): menuconfig M config C0 if M config C1 config C2 endif (4): menuconfig M config C0 config C1 depends on M config C2 depends on M”…”�”}”hj! sbah}”(h]”h ]”h"]”h$]”h&]”hühýuh1hìh³hÊh´M¨hjÙ h²hubhÝ)�”}”(hŒ choices::”h]”hŒchoices:”…”�”}”(hj/ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M¸hjÙ h²hubhí)�”}”(hŒ4"choice" "endchoice"”h]”hŒ4"choice" "endchoice"”…”�”}”hj= sbah}”(h]”h ]”h"]”h$]”h&]”hühýuh1hìh³hÊh´MºhjÙ h²hubhÝ)�”}”(hŒlThis defines a choice group and accepts "prompt", "default", "depends on", and "help" attributes as options.”h]”hŒ|This defines a choice group and accepts “promptâ€�, “defaultâ€�, “depends onâ€�, and “helpâ€� attributes as options.”…”�”}”(hjK h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M¿hjÙ h²hubhÝ)�”}”(hŒ:A choice only allows a single config entry to be selected.”h]”hŒ:A choice only allows a single config entry to be selected.”…”�”}”(hjY h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MÂhjÙ h²hubhÝ)�”}”(hŒ comment::”h]”hŒcomment:”…”�”}”(hjg h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MÄhjÙ h²hubhí)�”}”(hŒ$"comment" ”h]”hŒ$"comment" ”…”�”}”hju sbah}”(h]”h ]”h"]”h$]”h&]”hühýuh1hìh³hÊh´MÆhjÙ h²hubhÝ)�”}”(hŒªThis defines a comment which is displayed to the user during the configuration process and is also echoed to the output files. The only possible options are dependencies.”h]”hŒªThis defines a comment which is displayed to the user during the configuration process and is also echoed to the output files. The only possible options are dependencies.”…”�”}”(hjƒ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MÉhjÙ h²hubhÝ)�”}”(hŒmenu::”h]”hŒmenu:”…”�”}”(hj‘ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MÍhjÙ h²hubhí)�”}”(hŒ5"menu" "endmenu"”h]”hŒ5"menu" "endmenu"”…”�”}”hjŸ sbah}”(h]”h ]”h"]”h$]”h&]”hühýuh1hìh³hÊh´MÏhjÙ h²hubhÝ)�”}”(hŒ�This defines a menu block, see "Menu structure" above for more information. The only possible options are dependencies and "visible" attributes.”h]”hŒ˜This defines a menu block, see “Menu structureâ€� above for more information. The only possible options are dependencies and “visibleâ€� attributes.”…”�”}”(hj­ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MÔhjÙ h²hubhÝ)�”}”(hŒif::”h]”hŒif:”…”�”}”(hj» h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MØhjÙ h²hubhí)�”}”(hŒ"if" "endif"”h]”hŒ"if" "endif"”…”�”}”hjÉ sbah}”(h]”h ]”h"]”h$]”h&]”hühýuh1hìh³hÊh´MÚhjÙ h²hubhÝ)�”}”(hŒdThis defines an if block. The dependency expression is appended to all enclosed menu entries.”h]”hŒdThis defines an if block. The dependency expression is appended to all enclosed menu entries.”…”�”}”(hj× h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MÞhjÙ h²hubhÝ)�”}”(hŒsource::”h]”hŒsource:”…”�”}”(hjå h²h•Ûâh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MáhjÙ h²hubhí)�”}”(hŒ"source" ”h]”hŒ"source" ”…”�”}”hjó sbah}”(h]”h ]”h"]”h$]”h&]”hühýuh1hìh³hÊh´MãhjÙ h²hubhÝ)�”}”(hŒHThis reads the specified configuration file. This file is always parsed.”h]”hŒHThis reads the specified configuration file. This file is always parsed.”…”�”}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MåhjÙ h²hubhÝ)�”}”(hŒ mainmenu::”h]”hŒ mainmenu:”…”�”}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MçhjÙ h²hubhí)�”}”(hŒ"mainmenu" ”h]”hŒ"mainmenu" ”…”�”}”hj sbah}”(h]”h ]”h"]”h$]”h&]”hühýuh1hìh³hÊh´MéhjÙ h²hubhÝ)�”}”(hŒ¢This sets the config program's title bar if the config program chooses to use it. It should be placed at the top of the configuration, before any other statement.”h]”hŒ¤This sets the config program’s title bar if the config program chooses to use it. It should be placed at the top of the configuration, before any other statement.”…”�”}”(hj+ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MëhjÙ h²hubhÝ)�”}”(hŒ '#' Kconfig source file comment:”h]”hŒ$‘#’ Kconfig source file comment:”…”�”}”(hj9 h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MïhjÙ h²hubhÝ)�”}”(hŒ”An unquoted '#' character anywhere in a source file line indicates the beginning of a source file comment. The remainder of that line is a comment.”h]”hŒ˜An unquoted ‘#’ character anywhere in a source file line indicates the beginning of a source file comment. The remainder of that line is a comment.”…”�”}”(hjG h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MñhjÙ h²hubeh}”(h]”Œkconfig-syntax”ah ]”h"]”Œkconfig syntax”ah$]”h&]”uh1hµhh·h²hh³hÊh´Mrubh¶)�”}”(hhh]”(h»)�”}”(hŒ Kconfig hints”h]”hŒ Kconfig hints”…”�”}”(hj` h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj] h²hh³hÊh´M÷ubhÝ)�”}”(hŒ‘This is a collection of Kconfig tips, most of which aren't obvious at first glance and most of which have become idioms in several Kconfig files.”h]”hŒ“This is a collection of Kconfig tips, most of which aren’t obvious at first glance and most of which have become idioms in several Kconfig files.”…”�”}”(hjn h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Møhj] h²hubh¶)�”}”(hhh]”(h»)�”}”(hŒ6Adding common features and make the usage configurable”h]”hŒ6Adding common features and make the usage configurable”…”�”}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj| h²hh³hÊh´MýubhÝ)�”}”(hX9It is a common idiom to implement a feature/functionality that are relevant for some architectures but not all. The recommended way to do so is to use a config variable named HAVE_* that is defined in a common Kconfig file and selected by the relevant architectures. An example is the generic IOMAP functionality.”h]”hX9It is a common idiom to implement a feature/functionality that are relevant for some architectures but not all. The recommended way to do so is to use a config variable named HAVE_* that is defined in a common Kconfig file and selected by the relevant architectures. An example is the generic IOMAP functionality.”…”�”}”(hj� h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Mþhj| h²hubhÝ)�”}”(hŒWe would in lib/Kconfig see::”h]”hŒWe would in lib/Kconfig see:”…”�”}”(hj› h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Mhj| h²hubhí)�”}”(hŒy# Generic IOMAP is used to ... config HAVE_GENERIC_IOMAP config GENERIC_IOMAP depends on HAVE_GENERIC_IOMAP && FOO”h]”hŒy# Generic IOMAP is used to ... config HAVE_GENERIC_IOMAP config GENERIC_IOMAP depends on HAVE_GENERIC_IOMAP && FOO”…”�”}”hj© sbah}”(h]”h ]”h"]”h$]”h&]”hühýuh1hìh³hÊh´Mhj| h²hubhÝ)�”}”(hŒ"And in lib/Makefile we would see::”h]”hŒ!And in lib/Makefile we would see:”…”�”}”(hj· h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M hj| h²hubhí)�”}”(hŒ&obj-$(CONFIG_GENERIC_IOMAP) += iomap.o”h]”hŒ&obj-$(CONFIG_GENERIC_IOMAP) += iomap.o”…”�”}”hjÅ sbah}”(h]”h ]”h"]”h$]”h&]”hühýuh1hìh³hÊh´Mhj| h²hubhÝ)�”}”(hŒJFor each architecture using the generic IOMAP functionality we would see::”h]”hŒIFor each architecture using the generic IOMAP functionality we would see:”…”�”}”(hjÓ h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Mhj| h²hubhí)�”}”(hŒLconfig X86 select ... select HAVE_GENERIC_IOMAP select ...”h]”hŒLconfig X86 select ... select HAVE_GENERIC_IOMAP select ...”…”�”}”hjá sbah}”(h]”h ]”h"]”h$]”h&]”hühýuh1hìh³hÊh´Mhj| h²hubhÝ)�”}”(hŒnNote: we use the existing config option and avoid creating a new config variable to select HAVE_GENERIC_IOMAP.”h]”hŒnNote: we use the existing config option and avoid creating a new config variable to select HAVE_GENERIC_IOMAP.”…”�”}”(hjï h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Mhj| h²hubhÝ)�”}”(hX9Note: the use of the internal config variable HAVE_GENERIC_IOMAP, it is introduced to overcome the limitation of select which will force a config option to 'y' no matter the dependencies. The dependencies are moved to the symbol GENERIC_IOMAP and we avoid the situation where select forces a symbol equals to 'y'.”h]”hXANote: the use of the internal config variable HAVE_GENERIC_IOMAP, it is introduced to overcome the limitation of select which will force a config option to ‘y’ no matter the dependencies. The dependencies are moved to the symbol GENERIC_IOMAP and we avoid the situation where select forces a symbol equals to ‘y’.”…”�”}”(hjý h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Mhj| h²hubeh}”(h]”Œ6adding-common-features-and-make-the-usage-configurable”ah ]”h"]”Œ6adding common features and make the usage configurable”ah$]”h&]”uh1hµhj] h²hh³hÊh´Mýubh¶)�”}”(hhh]”(h»)�”}”(hŒ*Adding features that need compiler support”h]”hŒ*Adding features that need compiler support”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjh²hh³hÊh´M"ubhÝ)�”}”(hŒ¯There are several features that need compiler support. The recommended way to describe the dependency on the compiler feature is to use "depends on" followed by a test macro::”h]”hŒ²There are several features that need compiler support. The recommended way to describe the dependency on the compiler feature is to use “depends onâ€� followed by a test macro:”…”�”}”(hj$h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M$hjh²hubhí)�”}”(hŒ†config STACKPROTECTOR bool "Stack Protector buffer overflow detection" depends on $(cc-option,-fstack-protector) ...”h]”hŒ†config STACKPROTECTOR bool "Stack Protector buffer overflow detection" depends on $(cc-option,-fstack-protector) ...”…”�”}”hj2sbah}”(h]”h ]”h"]”h$]”h&]”hühýuh1hìh³hÊh´M(hjh²hubhÝ)�”}”(hŒ‹If you need to expose a compiler capability to makefiles and/or C source files, `CC_HAS_` is the recommended prefix for the config option::”h]”(hŒPIf you need to expose a compiler capability to makefiles and/or C source files, ”…”�”}”(hj@h²hh³Nh´NubhŒtitle_reference”“”)�”}”(hŒ `CC_HAS_`”h]”hŒCC_HAS_”…”�”}”(hjJh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jHhj@ubhŒ1 is the recommended prefix for the config option:”…”�”}”(hj@h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M-hjh²hubhí)�”}”(hŒTconfig CC_HAS_FOO def_bool $(success,$(srctree)/scripts/cc-check-foo.sh $(CC))”h]”hŒTconfig CC_HAS_FOO def_bool $(success,$(srctree)/scripts/cc-check-foo.sh $(CC))”…”�”}”hjbsbah}”(h]”h ]”h"]”h$]”h&]”hühýuh1hìh³hÊh´M0hjh²hubeh}”(h]”Œ*adding-features-that-need-compiler-support”ah ]”h"]”Œ*adding features that need compiler support”ah$]”h&]”uh1hµhj] h²hh³hÊh´M"ubh¶)�”}”(hhh]”(h»)�”}”(hŒBuild as module only”h]”hŒBuild as module only”…”�”}”(hj{h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjxh²hh³hÊh´M4ubhÝ)�”}”(hŒdTo restrict a component build to module-only, qualify its config symbol with "depends on m". E.g.::”h]”hŒgTo restrict a component build to module-only, qualify its config symbol with “depends on mâ€�. E.g.:”…”�”}”(hj‰h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M5hjxh²hubhí)�”}”(hŒ$config FOO depends on BAR && m”h]”hŒ$config FOO depends on BAR && m”…”�”}”hj—sbah}”(h]”h ]”h"]”h$]”h&]”hühýuh1hìh³hÊh´M8hjxh²hubhÝ)�”}”(hŒ+limits FOO to module (=m) or disabled (=n).”h]”hŒ+limits FOO to module (=m) or disabled (=n).”…”�”}”(hj¥h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M;hjxh²hubeh}”(h]”Œbuild-as-module-only”ah ]”h"]”Œbuild as module only”ah$]”h&]”uh1hµhj] h²hh³hÊh´M4ubh¶)�”}”(hhh]”(h»)�”}”(hŒCompile-testing”h]”hŒCompile-testing”…”�”}”(hj¾h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj»h²hh³hÊh´M>ubhÝ)�”}”(hX If a config symbol has a dependency, but the code controlled by the config symbol can still be compiled if the dependency is not met, it is encouraged to increase build coverage by adding an "|| COMPILE_TEST" clause to the dependency. This is especially useful for drivers for more exotic hardware, as it allows continuous-integration systems to compile-test the code on a more common system, and detect bugs that way. Note that compile-tested code should avoid crashing when run on a system where the dependency is not met.”h]”hXIf a config symbol has a dependency, but the code controlled by the config symbol can still be compiled if the dependency is not met, it is encouraged to increase build coverage by adding an “|| COMPILE_TESTâ€� clause to the dependency. This is especially useful for drivers for more exotic hardware, as it allows continuous-integration systems to compile-test the code on a more common system, and detect bugs that way. Note that compile-tested code should avoid crashing when run on a system where the dependency is not met.”…”�”}”(hjÌh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M?hj»h²hubeh}”(h]”Œcompile-testing”ah ]”h"]”Œcompile-testing”ah$]”h&]”uh1hµhj] h²hh³hÊh´M>ubh¶)�”}”(hhh]”(h»)�”}”(hŒ&Architecture and platform dependencies”h]”hŒ&Architecture and platform dependencies”…”�”}”(hjåh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjâh²hh³hÊh´MIubhÝ)�”}”(hX_Due to the presence of stubs, most drivers can now be compiled on most architectures. However, this does not mean it makes sense to have all drivers available everywhere, as the actual hardware may only exist on specific architectures and platforms. This is especially true for on-SoC IP cores, which may be limited to a specific vendor or SoC family.”h]”hX_Due to the presence of stubs, most drivers can now be compiled on most architectures. However, this does not mean it makes sense to have all drivers available everywhere, as the actual hardware may only exist on specific architectures and platforms. This is especially true for on-SoC IP cores, which may be limited to a specific vendor or SoC family.”…”�”}”(hjóh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MJhjâh²hubhÝ)�”}”(hX"To prevent asking the user about drivers that cannot be used on the system(s) the user is compiling a kernel for, and if it makes sense, config symbols controlling the compilation of a driver should contain proper dependencies, limiting the visibility of the symbol to (a superset of) the platform(s) the driver can be used on. The dependency can be an architecture (e.g. ARM) or platform (e.g. ARCH_OMAP4) dependency. This makes life simpler not only for distro config owners, but also for every single developer or user who configures a kernel.”h]”hX"To prevent asking the user about drivers that cannot be used on the system(s) the user is compiling a kernel for, and if it makes sense, config symbols controlling the compilation of a driver should contain proper dependencies, limiting the visibility of the symbol to (a superset of) the platform(s) the driver can be used on. The dependency can be an architecture (e.g. ARM) or platform (e.g. ARCH_OMAP4) dependency. This makes life simpler not only for distro config owners, but also for every single developer or user who configures a kernel.”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MPhjâh²hubhÝ)�”}”(hŒaSuch a dependency can be relaxed by combining it with the compile-testing rule above, leading to:”h]”hŒaSuch a dependency can be relaxed by combining it with the compile-testing rule above, leading to:”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MYhjâh²hubj6)�”}”(hŒbconfig FOO bool "Support for foo hardware" depends on ARCH_FOO_VENDOR || COMPILE_TEST ”h]”jJ)�”}”(hhh]”jO)�”}”(hŒVconfig FOO bool "Support for foo hardware" depends on ARCH_FOO_VENDOR || COMPILE_TEST ”h]”(jU)�”}”(hŒ config FOO”h]”hŒ config FOO”…”�”}”(hj(h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1jTh³hÊh´M^hj$ubje)�”}”(hhh]”hÝ)�”}”(hŒJbool "Support for foo hardware" depends on ARCH_FOO_VENDOR || COMPILE_TEST”h]”hŒNbool “Support for foo hardwareâ€� depends on ARCH_FOO_VENDOR || COMPILE_TEST”…”�”}”(hj9h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M]hj6ubah}”(h]”h ]”h"]”h$]”h&]”uh1jdhj$ubeh}”(h]”h ]”h"]”h$]”h&]”uh1jNh³hÊh´M^hj!ubah}”(h]”h ]”h"]”h$]”h&]”uh1jIhjubah}”(h]”h ]”h"]”h$]”h&]”uh1j5h³hÊh´M\hjâh²hubeh}”(h]”Œ&architecture-and-platform-dependencies”ah ]”h"]”Œ&architecture and platform dependencies”ah$]”h&]”uh1hµhj] h²hh³hÊh´MIubh¶)�”}”(hhh]”(h»)�”}”(hŒOptional dependencies”h]”hŒOptional dependencies”…”�”}”(hjjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjgh²hh³hÊh´MaubhÝ)�”}”(hŒÊSome drivers are able to optionally use a feature from another module or build cleanly with that module disabled, but cause a link failure when trying to use that loadable module from a built-in driver.”h]”hŒÊSome drivers are able to optionally use a feature from another module or build cleanly with that module disabled, but cause a link failure when trying to use that loadable module from a built-in driver.”…”�”}”(hjxh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Mchjgh²hubhÝ)�”}”(hŒdThe recommended way to express this optional dependency in Kconfig logic uses the conditional form::”h]”hŒcThe recommended way to express this optional dependency in Kconfig logic uses the conditional form:”…”�”}”(hj†h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Mghjgh²hubhí)�”}”(hŒPconfig FOO tristate "Support for foo hardware" depends on BAR if BAR”h]”hŒPconfig FOO tristate "Support for foo hardware" depends on BAR if BAR”…”�”}”hj”sbah}”(h]”h ]”h"]”h$]”h&]”hühýuh1hìh³hÊh´Mjhjgh²hubhÝ)�”}”(hŒ:This slightly counterintuitive style is also widely used::”h]”hŒ9This slightly counterintuitive style is also widely used:”…”�”}”(hj¢h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Mnhjgh²hubhí)�”}”(hŒQconfig FOO tristate "Support for foo hardware" depends on BAR || !BAR”h]”hŒQconfig FOO tristate "Support for foo hardware" depends on BAR || !BAR”…”�”}”hj°sbah}”(h]”h ]”h"]”h$]”h&]”hühýuh1hìh³hÊh´Mphjgh²hubhÝ)�”}”(hŒ¿This means that there is either a dependency on BAR that disallows the combination of FOO=y with BAR=m, or BAR is completely disabled. The BAR module must provide all the stubs for !BAR case.”h]”hŒ¿This means that there is either a dependency on BAR that disallows the combination of FOO=y with BAR=m, or BAR is completely disabled. The BAR module must provide all the stubs for !BAR case.”…”�”}”(hj¾h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Mthjgh²hubhÝ)�”}”(hŒFor a more formalized approach if there are multiple drivers that have the same dependency, a helper symbol can be used, like::”h]”hŒ~For a more formalized approach if there are multiple drivers that have the same dependency, a helper symbol can be used, like:”…”�”}”(hjÌh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Mxhjgh²hubhí)�”}”(hŒ†config FOO tristate "Support for foo hardware" depends on BAR_OPTIONAL config BAR_OPTIONAL def_tristate BAR || !BAR”h]”hŒ†config FOO tristate "Support for foo hardware" depends on BAR_OPTIONAL config BAR_OPTIONAL def_tristate BAR || !BAR”…”�”}”hjÚsbah}”(h]”h ]”h"]”h$]”h&]”hühýuh1hìh³hÊh´M{hjgh²hubhÝ)�”}”(hŒ¥Much less favorable way to express optional dependency is IS_REACHABLE() within the module code, useful for example when the module BAR does not provide !BAR stubs::”h]”hŒ¤Much less favorable way to express optional dependency is IS_REACHABLE() within the module code, useful for example when the module BAR does not provide !BAR stubs:”…”�”}”(hjèh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M‚hjgh²hubhí)�”}”(hŒdfoo_init() { if (IS_REACHABLE(CONFIG_BAR)) bar_register(&foo); ... }”h]”hŒdfoo_init() { if (IS_REACHABLE(CONFIG_BAR)) bar_register(&foo); ... }”…”�”}”hjösbah}”(h]”h ]”h"]”h$]”h&]”hühýuh1hìh³hÊh´M†hjgh²hubhÝ)�”}”(hŒÅIS_REACHABLE() is generally discouraged, because the code will be silently discarded, when CONFIG_BAR=m and this code is built-in. This is not what users usually expect when enabling BAR as module.”h]”hŒÅIS_REACHABLE() is generally discouraged, because the code will be silently discarded, when CONFIG_BAR=m and this code is built-in. This is not what users usually expect when enabling BAR as module.”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M�hjgh²hubeh}”(h]”Œoptional-dependencies”ah ]”h"]”Œoptional dependencies”ah$]”h&]”uh1hµhj] h²hh³hÊh´Maubh¶)�”}”(hhh]”(h»)�”}”(hŒ(Kconfig recursive dependency limitations”h]”hŒ(Kconfig recursive dependency limitations”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjh²hh³hÊh´M’ubhÝ)�”}”(hX‰If you've hit the Kconfig error: "recursive dependency detected" you've run into a recursive dependency issue with Kconfig, a recursive dependency can be summarized as a circular dependency. The kconfig tools need to ensure that Kconfig files comply with specified configuration requirements. In order to do that kconfig must determine the values that are possible for all Kconfig symbols, this is currently not possible if there is a circular relation between two or more Kconfig symbols. For more details refer to the "Simple Kconfig recursive issue" subsection below. Kconfig does not do recursive dependency resolution; this has a few implications for Kconfig file writers. We'll first explain why this issues exists and then provide an example technical limitation which this brings upon Kconfig developers. Eager developers wishing to try to address this limitation should read the next subsections.”h]”hX—If you’ve hit the Kconfig error: “recursive dependency detectedâ€� you’ve run into a recursive dependency issue with Kconfig, a recursive dependency can be summarized as a circular dependency. The kconfig tools need to ensure that Kconfig files comply with specified configuration requirements. In order to do that kconfig must determine the values that are possible for all Kconfig symbols, this is currently not possible if there is a circular relation between two or more Kconfig symbols. For more details refer to the “Simple Kconfig recursive issueâ€� subsection below. Kconfig does not do recursive dependency resolution; this has a few implications for Kconfig file writers. We’ll first explain why this issues exists and then provide an example technical limitation which this brings upon Kconfig developers. Eager developers wishing to try to address this limitation should read the next subsections.”…”�”}”(hj+h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M”hjh²hubeh}”(h]”Œ(kconfig-recursive-dependency-limitations”ah ]”h"]”Œ(kconfig recursive dependency limitations”ah$]”h&]”uh1hµhj] h²hh³hÊh´M’ubh¶)�”}”(hhh]”(h»)�”}”(hŒSimple Kconfig recursive issue”h]”hŒSimple Kconfig recursive issue”…”�”}”(hjDh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjAh²hh³hÊh´M£ubhÝ)�”}”(hŒ5Read: Documentation/kbuild/Kconfig.recursion-issue-01”h]”hŒ5Read: Documentation/kbuild/Kconfig.recursion-issue-01”…”�”}”(hjRh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M¥hjAh²hubhÝ)�”}”(hŒ Test with::”h]”hŒ Test with:”…”�”}”(hj`h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M§hjAh²hubhí)�”}”(hŒOmake KBUILD_KCONFIG=Documentation/kbuild/Kconfig.recursion-issue-01 allnoconfig”h]”hŒOmake KBUILD_KCONFIG=Documentation/kbuild/Kconfig.recursion-issue-01 allnoconfig”…”�”}”hjnsbah}”(h]”h ]”h"]”h$]”h&]”hühýuh1hìh³hÊh´M©hjAh²hubeh}”(h]”Œsimple-kconfig-recursive-issue”ah ]”h"]”Œsimple kconfig recursive issue”ah$]”h&]”uh1hµhj] h²hh³hÊh´M£ubh¶)�”}”(hhh]”(h»)�”}”(hŒ"Cumulative Kconfig recursive issue”h]”hŒ"Cumulative Kconfig recursive issue”…”�”}”(hj‡h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj„h²hh³hÊh´M¬ubhÝ)�”}”(hŒ5Read: Documentation/kbuild/Kconfig.recursion-issue-02”h]”hŒ5Read: Documentation/kbuild/Kconfig.recursion-issue-02”…”�”}”(hj•h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M®hj„h²hubhÝ)�”}”(hŒ Test with::”h]”hŒ Test with:”…”�”}”(hj£h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M°hj„h²hubhí)�”}”(hŒOmake KBUILD_KCONFIG=Documentation/kbuild/Kconfig.recursion-issue-02 allnoconfig”h]”hŒOmake KBUILD_KCONFIG=Documentation/kbuild/Kconfig.recursion-issue-02 allnoconfig”…”�”}”hj±sbah}”(h]”h ]”h"]”h$]”h&]”hühýuh1hìh³hÊh´M²hj„h²hubeh}”(h]”Œ"cumulative-kconfig-recursive-issue”ah ]”h"]”Œ"cumulative kconfig recursive issue”ah$]”h&]”uh1hµhj] h²hh³hÊh´M¬ubh¶)�”}”(hhh]”(h»)�”}”(hŒ.Practical solutions to kconfig recursive issue”h]”hŒ.Practical solutions to kconfig recursive issue”…”�”}”(hjÊh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjÇh²hh³hÊh´MµubhÝ)�”}”(hŒÇDevelopers who run into the recursive Kconfig issue have two options at their disposal. We document them below and also provide a list of historical issues resolved through these different solutions.”h]”hŒÇDevelopers who run into the recursive Kconfig issue have two options at their disposal. We document them below and also provide a list of historical issues resolved through these different solutions.”…”�”}”(hjØh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M·hjÇh²hubj6)�”}”(hŒÈa) Remove any superfluous "select FOO" or "depends on FOO" b) Match dependency semantics: b1) Swap all "select FOO" to "depends on FOO" or, b2) Swap all "depends on FOO" to "select FOO" ”h]”jx)�”}”(hhh]”(j|)�”}”(hŒ7Remove any superfluous "select FOO" or "depends on FOO"”h]”hÝ)�”}”(hjïh]”hŒ?Remove any superfluous “select FOOâ€� or “depends on FOOâ€�”…”�”}”(hjñh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M»hjíubah}”(h]”h ]”h"]”h$]”h&]”uh1j{hjêubj|)�”}”(hŒ„Match dependency semantics: b1) Swap all "select FOO" to "depends on FOO" or, b2) Swap all "depends on FOO" to "select FOO" ”h]”(hÝ)�”}”(hŒMatch dependency semantics:”h]”hŒMatch dependency semantics:”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M¼hjubj6)�”}”(hŒab1) Swap all "select FOO" to "depends on FOO" or, b2) Swap all "depends on FOO" to "select FOO" ”h]”(hÝ)�”}”(hŒ1b1) Swap all "select FOO" to "depends on FOO" or,”h]”hŒ9b1) Swap all “select FOOâ€� to “depends on FOOâ€� or,”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M¾hjubhÝ)�”}”(hŒ-b2) Swap all "depends on FOO" to "select FOO"”h]”hŒ5b2) Swap all “depends on FOOâ€� to “select FOOâ€�”…”�”}”(hj(h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MÀhjubeh}”(h]”h ]”h"]”h$]”h&]”uh1j5h³hÊh´M¾hjubeh}”(h]”h ]”h"]”h$]”h&]”uh1j{hjêubeh}”(h]”h ]”h"]”h$]”h&]”jâjãjähjåjæuh1jwhjæubah}”(h]”h ]”h"]”h$]”h&]”uh1j5h³hÊh´M»hjÇh²hubhÝ)�”}”(hXcThe resolution to a) can be tested with the sample Kconfig file Documentation/kbuild/Kconfig.recursion-issue-01 through the removal of the "select CORE" from CORE_BELL_A_ADVANCED as that is implicit already since CORE_BELL_A depends on CORE. At times it may not be possible to remove some dependency criteria, for such cases you can work with solution b).”h]”hXgThe resolution to a) can be tested with the sample Kconfig file Documentation/kbuild/Kconfig.recursion-issue-01 through the removal of the “select COREâ€� from CORE_BELL_A_ADVANCED as that is implicit already since CORE_BELL_A depends on CORE. At times it may not be possible to remove some dependency criteria, for such cases you can work with solution b).”…”�”}”(hjNh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MÂhjÇh²hubhÝ)�”}”(hŒ~The two different resolutions for b) can be tested in the sample Kconfig file Documentation/kbuild/Kconfig.recursion-issue-02.”h]”hŒ~The two different resolutions for b) can be tested in the sample Kconfig file Documentation/kbuild/Kconfig.recursion-issue-02.”…”�”}”(hj\h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MÈhjÇh²hubhÝ)�”}”(hŒªBelow is a list of examples of prior fixes for these types of recursive issues; all errors appear to involve one or more "select" statements and one or more "depends on".”h]”hŒ²Below is a list of examples of prior fixes for these types of recursive issues; all errors appear to involve one or more “selectâ€� statements and one or more “depends onâ€�.”…”�”}”(hjjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MËhjÇh²hubjk)�”}”(hhh]”jp)�”}”(hhh]”(ju)�”}”(hhh]”h}”(h]”h ]”h"]”h$]”h&]”Œcolwidth”K uh1jthj{ubju)�”}”(hhh]”h}”(h]”h ]”h"]”h$]”h&]”Œcolwidth”K#uh1jthj{ubjŸ)�”}”(hhh]”j¤)�”}”(hhh]”(j©)�”}”(hhh]”hÝ)�”}”(hŒcommit”h]”hŒcommit”…”�”}”(hj›h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MÐhj˜ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hj•ubj©)�”}”(hhh]”hÝ)�”}”(hŒfix”h]”hŒfix”…”�”}”(hj²h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MÐhj¯ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hj•ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j£hj’ubah}”(h]”h ]”h"]”h$]”h&]”uh1jžhj{ubj)�”}”(hhh]”(j¤)�”}”(hhh]”(j©)�”}”(hhh]”hÝ)�”}”(hŒ 06b718c01208”h]”hŒ 06b718c01208”…”�”}”(hjÛh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MÒhjØubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hjÕubj©)�”}”(hhh]”hÝ)�”}”(hŒselect A -> depends on A”h]”hŒselect A -> depends on A”…”�”}”(hjòh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MÒhjïubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hjÕubeh}”(h]”h ]”h"]”h$]”h&]”uh1j£hjÒubj¤)�”}”(hhh]”(j©)�”}”(hhh]”hÝ)�”}”(hŒ c22eacfe82f9”h]”hŒ c22eacfe82f9”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MÓhjubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hj ubj©)�”}”(hhh]”hÝ)�”}”(hŒdepends on A -> depends on B”h]”hŒdepends on A -> depends on B”…”�”}”(hj)h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MÓhj&ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hj ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j£hjÒubj¤)�”}”(hhh]”(j©)�”}”(hhh]”hÝ)�”}”(hŒ 6a91e854442c”h]”hŒ 6a91e854442c”…”�”}”(hjIh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MÔhjFubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hjCubj©)�”}”(hhh]”hÝ)�”}”(hŒselect A -> depends on A”h]”hŒselect A -> depends on A”…”�”}”(hj`h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MÔhj]ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hjCubeh}”(h]”h ]”h"]”h$]”h&]”uh1j£hjÒubj¤)�”}”(hhh]”(j©)�”}”(hhh]”hÝ)�”}”(hŒ 118c565a8f2e”h]”hŒ 118c565a8f2e”…”�”}”(hj€h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MÕhj}ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hjzubj©)�”}”(hhh]”hÝ)�”}”(hŒselect A -> select B”h]”hŒselect A -> select B”…”�”}”(hj—h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MÕhj”ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hjzubeh}”(h]”h ]”h"]”h$]”h&]”uh1j£hjÒubj¤)�”}”(hhh]”(j©)�”}”(hhh]”hÝ)�”}”(hŒ f004e5594705”h]”hŒ f004e5594705”…”�”}”(hj·h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MÖhj´ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hj±ubj©)�”}”(hhh]”hÝ)�”}”(hŒselect A -> depends on A”h]”hŒselect A -> depends on A”…”�”}”(hjÎh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MÖhjËubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hj±ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j£hjÒubj¤)�”}”(hhh]”(j©)�”}”(hhh]”hÝ)�”}”(hŒ c7861f37b4c6”h]”hŒ c7861f37b4c6”…”�”}”(hjîh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M×hjëubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hjèubj©)�”}”(hhh]”hÝ)�”}”(hŒdepends on A -> (null)”h]”hŒdepends on A -> (null)”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M×hjubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hjèubeh}”(h]”h ]”h"]”h$]”h&]”uh1j£hjÒubj¤)�”}”(hhh]”(j©)�”}”(hhh]”hÝ)�”}”(hŒ 80c69915e5fb”h]”hŒ 80c69915e5fb”…”�”}”(hj%h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MØhj"ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hjubj©)�”}”(hhh]”hÝ)�”}”(hŒ#select A -> (null) (1)”h]”hŒ#select A -> (null) (1)”…”�”}”(hj<h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MØhj9ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hjubeh}”(h]”h ]”h"]”h$]”h&]”uh1j£hjÒubj¤)�”}”(hhh]”(j©)�”}”(hhh]”hÝ)�”}”(hŒ c2218e26c0d0”h]”hŒ c2218e26c0d0”…”�”}”(hj\h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MÙhjYubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hjVubj©)�”}”(hhh]”hÝ)�”}”(hŒ#select A -> depends on A (1)”h]”hŒ#select A -> depends on A (1)”…”�”}”(hjsh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MÙhjpubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hjVubeh}”(h]”h ]”h"]”h$]”h&]”uh1j£hjÒubj¤)�”}”(hhh]”(j©)�”}”(hhh]”hÝ)�”}”(hŒ d6ae99d04e1c”h]”hŒ d6ae99d04e1c”…”�”}”(hj“h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MÚhj�ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hj�ubj©)�”}”(hhh]”hÝ)�”}”(hŒselect A -> depends on A”h]”hŒselect A -> depends on A”…”�”}”(hjªh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MÚhj§ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hj�ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j£hjÒubj¤)�”}”(hhh]”(j©)�”}”(hhh]”hÝ)�”}”(hŒ 95ca19cf8cbf”h]”hŒ 95ca19cf8cbf”…”�”}”(hjÊh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MÛhjÇubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hjÄubj©)�”}”(hhh]”hÝ)�”}”(hŒselect A -> depends on A”h]”hŒselect A -> depends on A”…”�”}”(hjáh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MÛhjÞubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hjÄubeh}”(h]”h ]”h"]”h$]”h&]”uh1j£hjÒubj¤)�”}”(hhh]”(j©)�”}”(hhh]”hÝ)�”}”(hŒ 8f057d7bca54”h]”hŒ 8f057d7bca54”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MÜhjþubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hjûubj©)�”}”(hhh]”hÝ)�”}”(hŒdepends on A -> (null)”h]”hŒdepends on A -> (null)”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MÜhjubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hjûubeh}”(h]”h ]”h"]”h$]”h&]”uh1j£hjÒubj¤)�”}”(hhh]”(j©)�”}”(hhh]”hÝ)�”}”(hŒ 8f057d7bca54”h]”hŒ 8f057d7bca54”…”�”}”(hj8h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MÝhj5ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hj2ubj©)�”}”(hhh]”hÝ)�”}”(hŒdepends on A -> select A”h]”hŒdepends on A -> select A”…”�”}”(hjOh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MÝhjLubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hj2ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j£hjÒubj¤)�”}”(hhh]”(j©)�”}”(hhh]”hÝ)�”}”(hŒ a0701f04846e”h]”hŒ a0701f04846e”…”�”}”(hjoh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MÞhjlubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hjiubj©)�”}”(hhh]”hÝ)�”}”(hŒselect A -> depends on A”h]”hŒselect A -> depends on A”…”�”}”(hj†h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MÞhjƒubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hjiubeh}”(h]”h ]”h"]”h$]”h&]”uh1j£hjÒubj¤)�”}”(hhh]”(j©)�”}”(hhh]”hÝ)�”}”(hŒ 0c8b92f7f259”h]”hŒ 0c8b92f7f259”…”�”}”(hj¦h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Mßhj£ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hj ubj©)�”}”(hhh]”hÝ)�”}”(hŒdepends on A -> (null)”h]”hŒdepends on A -> (null)”…”�”}”(hj½h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Mßhjºubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hj ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j£hjÒubj¤)�”}”(hhh]”(j©)�”}”(hhh]”hÝ)�”}”(hŒ e4e9e0540928”h]”hŒ e4e9e0540928”…”�”}”(hjÝh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MàhjÚubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hj×ubj©)�”}”(hhh]”hÝ)�”}”(hŒ#select A -> depends on A (2)”h]”hŒ#select A -> depends on A (2)”…”�”}”(hjôh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Màhjñubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hj×ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j£hjÒubj¤)�”}”(hhh]”(j©)�”}”(hhh]”hÝ)�”}”(hŒ 7453ea886e87”h]”hŒ 7453ea886e87”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Máhjubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hjubj©)�”}”(hhh]”hÝ)�”}”(hŒ#depends on A > (null) (1)”h]”hŒ#depends on A > (null) (1)”…”�”}”(hj+h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Máhj(ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hjubeh}”(h]”h ]”h"]”h$]”h&]”uh1j£hjÒubj¤)�”}”(hhh]”(j©)�”}”(hhh]”hÝ)�”}”(hŒ 7b1fff7e4fdf”h]”hŒ 7b1fff7e4fdf”…”�”}”(hjKh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MâhjHubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hjEubj©)�”}”(hhh]”hÝ)�”}”(hŒselect A -> depends on A”h]”hŒselect A -> depends on A”…”�”}”(hjbh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Mâhj_ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hjEubeh}”(h]”h ]”h"]”h$]”h&]”uh1j£hjÒubj¤)�”}”(hhh]”(j©)�”}”(hhh]”hÝ)�”}”(hŒ 86c747d2a4f0”h]”hŒ 86c747d2a4f0”…”�”}”(hj‚h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Mãhjubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hj|ubj©)�”}”(hhh]”hÝ)�”}”(hŒselect A -> depends on A”h]”hŒselect A -> depends on A”…”�”}”(hj™h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Mãhj–ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hj|ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j£hjÒubj¤)�”}”(hhh]”(j©)�”}”(hhh]”hÝ)�”}”(hŒ d9f9ab51e55e”h]”hŒ d9f9ab51e55e”…”�”}”(hj¹h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Mähj¶ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hj³ubj©)�”}”(hhh]”hÝ)�”}”(hŒselect A -> depends on A”h]”hŒselect A -> depends on A”…”�”}”(hjÐh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MähjÍubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hj³ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j£hjÒubj¤)�”}”(hhh]”(j©)�”}”(hhh]”hÝ)�”}”(hŒ 0c51a4d8abd6”h]”hŒ 0c51a4d8abd6”…”�”}”(hjðh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Måhjíubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hjêubj©)�”}”(hhh]”hÝ)�”}”(hŒ#depends on A -> select A (3)”h]”hŒ#depends on A -> select A (3)”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Måhjubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hjêubeh}”(h]”h ]”h"]”h$]”h&]”uh1j£hjÒubj¤)�”}”(hhh]”(j©)�”}”(hhh]”hÝ)�”}”(hŒ e98062ed6dc4”h]”hŒ e98062ed6dc4”…”�”}”(hj'h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Mæhj$ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hj!ubj©)�”}”(hhh]”hÝ)�”}”(hŒ#select A -> depends on A (3)”h]”hŒ#select A -> depends on A (3)”…”�”}”(hj>h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Mæhj;ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hj!ubeh}”(h]”h ]”h"]”h$]”h&]”uh1j£hjÒubj¤)�”}”(hhh]”(j©)�”}”(hhh]”hÝ)�”}”(hŒ 91e5d284a7f1”h]”hŒ 91e5d284a7f1”…”�”}”(hj^h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Mçhj[ubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hjXubj©)�”}”(hhh]”hÝ)�”}”(hŒselect A -> (null)”h]”hŒselect A -> (null)”…”�”}”(hjuh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Mçhjrubah}”(h]”h ]”h"]”h$]”h&]”uh1j¨hjXubeh}”(h]”h ]”h"]”h$]”h&]”uh1j£hjÒubeh}”(h]”h ]”h"]”h$]”h&]”uh1jhj{ubeh}”(h]”h ]”h"]”h$]”h&]”Œcols”Kuh1johjxubah}”(h]”h ]”h"]”h$]”h&]”uh1jjhjÇh²hh³hÊh´Nubjx)�”}”(hhh]”(j|)�”}”(hŒPartial (or no) quote of error.”h]”hÝ)�”}”(hj§h]”hŒPartial (or no) quote of error.”…”�”}”(hj©h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Mêhj¥ubah}”(h]”h ]”h"]”h$]”h&]”uh1j{hj¢h²hh³hÊh´Nubj|)�”}”(hŒ&That seems to be the gist of that fix.”h]”hÝ)�”}”(hj¾h]”hŒ&That seems to be the gist of that fix.”…”�”}”(hjÀh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Mëhj¼ubah}”(h]”h ]”h"]”h$]”h&]”uh1j{hj¢h²hh³hÊh´Nubj|)�”}”(hŒ Same error. ”h]”hÝ)�”}”(hŒ Same error.”h]”hŒ Same error.”…”�”}”(hj×h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MìhjÓubah}”(h]”h ]”h"]”h$]”h&]”uh1j{hj¢h²hh³hÊh´Nubeh}”(h]”h ]”h"]”h$]”h&]”jâj jäj jåjæuh1jwhjÇh²hh³hÊh´Mêubeh}”(h]”Œ.practical-solutions-to-kconfig-recursive-issue”ah ]”h"]”Œ.practical solutions to kconfig recursive issue”ah$]”h&]”uh1hµhj] h²hh³hÊh´Mµubh¶)�”}”(hhh]”(h»)�”}”(hŒFuture kconfig work”h]”hŒFuture kconfig work”…”�”}”(hjüh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjùh²hh³hÊh´MïubhÝ)�”}”(hXÆWork on kconfig is welcomed on both areas of clarifying semantics and on evaluating the use of a full SAT solver for it. A full SAT solver can be desirable to enable more complex dependency mappings and / or queries, for instance one possible use case for a SAT solver could be that of handling the current known recursive dependency issues. It is not known if this would address such issues but such evaluation is desirable. If support for a full SAT solver proves too complex or that it cannot address recursive dependency issues Kconfig should have at least clear and well defined semantics which also addresses and documents limitations or requirements such as the ones dealing with recursive dependencies.”h]”hXÆWork on kconfig is welcomed on both areas of clarifying semantics and on evaluating the use of a full SAT solver for it. A full SAT solver can be desirable to enable more complex dependency mappings and / or queries, for instance one possible use case for a SAT solver could be that of handling the current known recursive dependency issues. It is not known if this would address such issues but such evaluation is desirable. If support for a full SAT solver proves too complex or that it cannot address recursive dependency issues Kconfig should have at least clear and well defined semantics which also addresses and documents limitations or requirements such as the ones dealing with recursive dependencies.”…”�”}”(hj h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Mñhjùh²hubhÝ)�”}”(hŒvFurther work on both of these areas is welcomed on Kconfig. We elaborate on both of these in the next two subsections.”h]”hŒvFurther work on both of these areas is welcomed on Kconfig. We elaborate on both of these in the next two subsections.”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Mühjùh²hubeh}”(h]”Œfuture-kconfig-work”ah ]”h"]”Œfuture kconfig work”ah$]”h&]”uh1hµhj] h²hh³hÊh´Mïubh¶)�”}”(hhh]”(h»)�”}”(hŒSemantics of Kconfig”h]”hŒSemantics of Kconfig”…”�”}”(hj1h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhj.h²hh³hÊh´MubhÝ)�”}”(hX_The use of Kconfig is broad, Linux is now only one of Kconfig's users: one study has completed a broad analysis of Kconfig use in 12 projects [0]_. Despite its widespread use, and although this document does a reasonable job in documenting basic Kconfig syntax a more precise definition of Kconfig semantics is welcomed. One project deduced Kconfig semantics through the use of the xconfig configurator [1]_. Work should be done to confirm if the deduced semantics matches our intended Kconfig design goals. Another project formalized a denotational semantics of a core subset of the Kconfig language [10]_.”h]”(hŒ�The use of Kconfig is broad, Linux is now only one of Kconfig’s users: one study has completed a broad analysis of Kconfig use in 12 projects ”…”�”}”(hj?h²hh³Nh´NubhŒfootnote_reference”“”)�”}”(hŒ[0]_”h]”hŒ0”…”�”}”(hjIh²hh³Nh´Nubah}”(h]”Œid1”ah ]”h"]”h$]”h&]”Œrefid”Œid10”Œdocname”Œkbuild/kconfig-language”uh1jGhj?Œresolved”KubhX. Despite its widespread use, and although this document does a reasonable job in documenting basic Kconfig syntax a more precise definition of Kconfig semantics is welcomed. One project deduced Kconfig semantics through the use of the xconfig configurator ”…”�”}”(hj?h²hh³Nh´NubjH)�”}”(hŒ[1]_”h]”hŒ1”…”�”}”(hjah²hh³Nh´Nubah}”(h]”Œid2”ah ]”h"]”h$]”h&]”jXŒid11”jZj[uh1jGhj?j\KubhŒÂ. Work should be done to confirm if the deduced semantics matches our intended Kconfig design goals. Another project formalized a denotational semantics of a core subset of the Kconfig language ”…”�”}”(hj?h²hh³Nh´NubjH)�”}”(hŒ[10]_”h]”hŒ10”…”�”}”(hjuh²hh³Nh´Nubah}”(h]”Œid3”ah ]”h"]”h$]”h&]”jXŒid26”jZj[uh1jGhj?j\KubhŒ.”…”�”}”(hj?h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Mhj.h²hubhÝ)�”}”(hXJHaving well defined semantics can be useful for tools for practical evaluation of dependencies, for instance one such case was work to express in boolean abstraction of the inferred semantics of Kconfig to translate Kconfig logic into boolean formulas and run a SAT solver on this to find dead code / features (always inactive), 114 dead features were found in Linux using this methodology [1]_ (Section 8: Threats to validity). The kismet tool, based on the semantics in [10]_, finds abuses of reverse dependencies and has led to dozens of committed fixes to Linux Kconfig files [11]_.”h]”(hX†Having well defined semantics can be useful for tools for practical evaluation of dependencies, for instance one such case was work to express in boolean abstraction of the inferred semantics of Kconfig to translate Kconfig logic into boolean formulas and run a SAT solver on this to find dead code / features (always inactive), 114 dead features were found in Linux using this methodology ”…”�”}”(hj�h²hh³Nh´NubjH)�”}”(hŒ[1]_”h]”hŒ1”…”�”}”(hj—h²hh³Nh´Nubah}”(h]”Œid4”ah ]”h"]”h$]”h&]”jXjpjZj[uh1jGhj�j\KubhŒN (Section 8: Threats to validity). The kismet tool, based on the semantics in ”…”�”}”(hj�h²hh³Nh´NubjH)�”}”(hŒ[10]_”h]”hŒ10”…”�”}”(hjªh²hh³Nh´Nubah}”(h]”Œid5”ah ]”h"]”h$]”h&]”jXj„jZj[uh1jGhj�j\KubhŒg, finds abuses of reverse dependencies and has led to dozens of committed fixes to Linux Kconfig files ”…”�”}”(hj�h²hh³Nh´NubjH)�”}”(hŒ[11]_”h]”hŒ11”…”�”}”(hj½h²hh³Nh´Nubah}”(h]”Œid6”ah ]”h"]”h$]”h&]”jXŒid27”jZj[uh1jGhj�j\KubhŒ.”…”�”}”(hj�h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M hj.h²hubhÝ)�”}”(hX©Confirming this could prove useful as Kconfig stands as one of the leading industrial variability modeling languages [1]_ [2]_. Its study would help evaluate practical uses of such languages, their use was only theoretical and real world requirements were not well understood. As it stands though only reverse engineering techniques have been used to deduce semantics from variability modeling languages such as Kconfig [3]_.”h]”(hŒuConfirming this could prove useful as Kconfig stands as one of the leading industrial variability modeling languages ”…”�”}”(hj×h²hh³Nh´NubjH)�”}”(hŒ[1]_”h]”hŒ1”…”�”}”(hjßh²hh³Nh´Nubah}”(h]”Œid7”ah ]”h"]”h$]”h&]”jXjpjZj[uh1jGhj×j\KubhŒ ”…”�”}”(hj×h²hh³Nh´NubjH)�”}”(hŒ[2]_”h]”hŒ2”…”�”}”(hjòh²hh³Nh´Nubah}”(h]”Œid8”ah ]”h"]”h$]”h&]”jXŒid12”jZj[uh1jGhj×j\KubhX&. Its study would help evaluate practical uses of such languages, their use was only theoretical and real world requirements were not well understood. As it stands though only reverse engineering techniques have been used to deduce semantics from variability modeling languages such as Kconfig ”…”�”}”(hj×h²hh³Nh´NubjH)�”}”(hŒ[3]_”h]”hŒ3”…”�”}”(hjh²hh³Nh´Nubah}”(h]”Œid9”ah ]”h"]”h$]”h&]”jXŒid13”jZj[uh1jGhj×j\KubhŒ.”…”�”}”(hj×h²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Mhj.h²hubhŒfootnote”“”)�”}”(hŒ9https://www.eng.uwaterloo.ca/~shshe/kconfig_semantics.pdf”h]”(hŒlabel”“”)�”}”(hŒ0”h]”hŒ0”…”�”}”(hj(h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j&hj"ubhÝ)�”}”(hj$h]”hŒ reference”“”)�”}”(hj$h]”hŒ9https://www.eng.uwaterloo.ca/~shshe/kconfig_semantics.pdf”…”�”}”(hj;h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”j$uh1j9hj6ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Mhj"ubeh}”(h]”jYah ]”h"]”Œ0”ah$]”h&]”jSajZj[uh1j h³hÊh´Mhj.h²hj\Kubj!)�”}”(hŒ?https://gsd.uwaterloo.ca/sites/default/files/vm-2013-berger.pdf”h]”(j')�”}”(hŒ1”h]”hŒ1”…”�”}”(hjZh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j&hjVubhÝ)�”}”(hjXh]”j:)�”}”(hjXh]”hŒ?https://gsd.uwaterloo.ca/sites/default/files/vm-2013-berger.pdf”…”�”}”(hjkh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”jXuh1j9hjhubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´MhjVubeh}”(h]”jpah ]”h"]”Œ1”ah$]”h&]”(jkj¡jéejZj[uh1j h³hÊh´Mhj.h²hj\Kubj!)�”}”(hŒ@https://gsd.uwaterloo.ca/sites/default/files/ase241-berger_0.pdf”h]”(j')�”}”(hŒ2”h]”hŒ2”…”�”}”(hjŠh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j&hj†ubhÝ)�”}”(hjˆh]”j:)�”}”(hjˆh]”hŒ@https://gsd.uwaterloo.ca/sites/default/files/ase241-berger_0.pdf”…”�”}”(hj›h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”jˆuh1j9hj˜ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Mhj†ubeh}”(h]”jah ]”h"]”Œ2”ah$]”h&]”jüajZj[uh1j h³hÊh´Mhj.h²hj\Kubj!)�”}”(hŒ:https://gsd.uwaterloo.ca/sites/default/files/icse2011.pdf ”h]”(j')�”}”(hŒ3”h]”hŒ3”…”�”}”(hjºh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j&hj¶ubhÝ)�”}”(hŒ9https://gsd.uwaterloo.ca/sites/default/files/icse2011.pdf”h]”j:)�”}”(hjÊh]”hŒ9https://gsd.uwaterloo.ca/sites/default/files/icse2011.pdf”…”�”}”(hjÌh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”jÊuh1j9hjÈubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´Mhj¶ubeh}”(h]”jah ]”h"]”Œ3”ah$]”h&]”jajZj[uh1j h³hÊh´Mhj.h²hj\Kubeh}”(h]”Œsemantics-of-kconfig”ah ]”h"]”Œsemantics of kconfig”ah$]”h&]”uh1hµhj] h²hh³hÊh´Mubh¶)�”}”(hhh]”(h»)�”}”(hŒFull SAT solver for Kconfig”h]”hŒFull SAT solver for Kconfig”…”�”}”(hjòh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1hºhjïh²hh³hÊh´M"ubhÝ)�”}”(hXâAlthough SAT solvers [4]_ haven't yet been used by Kconfig directly, as noted in the previous subsection, work has been done however to express in boolean abstraction the inferred semantics of Kconfig to translate Kconfig logic into boolean formulas and run a SAT solver on it [5]_. Another known related project is CADOS [6]_ (former VAMOS [7]_) and the tools, mainly undertaker [8]_, which has been introduced first with [9]_. The basic concept of undertaker is to extract variability models from Kconfig and put them together with a propositional formula extracted from CPP #ifdefs and build-rules into a SAT solver in order to find dead code, dead files, and dead symbols. If using a SAT solver is desirable on Kconfig one approach would be to evaluate repurposing such efforts somehow on Kconfig. There is enough interest from mentors of existing projects to not only help advise how to integrate this work upstream but also help maintain it long term. Interested developers should visit:”h]”(hŒAlthough SAT solvers ”…”�”}”(hjh²hh³Nh´NubjH)�”}”(hŒ[4]_”h]”hŒ4”…”�”}”(hjh²hh³Nh´Nubah}”(h]”Œid14”ah ]”h"]”h$]”h&]”jXŒid20”jZj[uh1jGhjj\KubhŒþ haven’t yet been used by Kconfig directly, as noted in the previous subsection, work has been done however to express in boolean abstraction the inferred semantics of Kconfig to translate Kconfig logic into boolean formulas and run a SAT solver on it ”…”�”}”(hjh²hh³Nh´NubjH)�”}”(hŒ[5]_”h]”hŒ5”…”�”}”(hjh²hh³Nh´Nubah}”(h]”Œid15”ah ]”h"]”h$]”h&]”jXŒid21”jZj[uh1jGhjj\KubhŒ). Another known related project is CADOS ”…”�”}”(hjh²hh³Nh´NubjH)�”}”(hŒ[6]_”h]”hŒ6”…”�”}”(hj0h²hh³Nh´Nubah}”(h]”Œid16”ah ]”h"]”h$]”h&]”jXŒid22”jZj[uh1jGhjj\KubhŒ (former VAMOS ”…”�”}”(hjh²hh³Nh´NubjH)�”}”(hŒ[7]_”h]”hŒ7”…”�”}”(hjDh²hh³Nh´Nubah}”(h]”Œid17”ah ]”h"]”h$]”h&]”jXŒid23”jZj[uh1jGhjj\KubhŒ#) and the tools, mainly undertaker ”…”�”}”(hjh²hh³Nh´NubjH)�”}”(hŒ[8]_”h]”hŒ8”…”�”}”(hjXh²hh³Nh´Nubah}”(h]”Œid18”ah ]”h"]”h$]”h&]”jXŒid24”jZj[uh1jGhjj\KubhŒ', which has been introduced first with ”…”�”}”(hjh²hh³Nh´NubjH)�”}”(hŒ[9]_”h]”hŒ9”…”�”}”(hjlh²hh³Nh´Nubah}”(h]”Œid19”ah ]”h"]”h$]”h&]”jXŒid25”jZj[uh1jGhjj\KubhX7. The basic concept of undertaker is to extract variability models from Kconfig and put them together with a propositional formula extracted from CPP #ifdefs and build-rules into a SAT solver in order to find dead code, dead files, and dead symbols. If using a SAT solver is desirable on Kconfig one approach would be to evaluate repurposing such efforts somehow on Kconfig. There is enough interest from mentors of existing projects to not only help advise how to integrate this work upstream but also help maintain it long term. Interested developers should visit:”…”�”}”(hjh²hh³Nh´Nubeh}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M$hjïh²hubhÝ)�”}”(hŒ4https://kernelnewbies.org/KernelProjects/kconfig-sat”h]”j:)�”}”(hjˆh]”hŒ4https://kernelnewbies.org/KernelProjects/kconfig-sat”…”�”}”(hjŠh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”jˆuh1j9hj†ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M2hjïh²hubj!)�”}”(hŒFhttps://www.cs.cornell.edu/~sabhar/chapters/SATSolvers-KR-Handbook.pdf”h]”(j')�”}”(hŒ4”h]”hŒ4”…”�”}”(hj¢h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j&hjžubhÝ)�”}”(hj h]”j:)�”}”(hj h]”hŒFhttps://www.cs.cornell.edu/~sabhar/chapters/SATSolvers-KR-Handbook.pdf”…”�”}”(hj³h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”j uh1j9hj°ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M4hjžubeh}”(h]”jah ]”h"]”Œ4”ah$]”h&]”jajZj[uh1j h³hÊh´M4hjïh²hj\Kubj!)�”}”(hŒ?https://gsd.uwaterloo.ca/sites/default/files/vm-2013-berger.pdf”h]”(j')�”}”(hŒ5”h]”hŒ5”…”�”}”(hjÒh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j&hjÎubhÝ)�”}”(hjÐh]”j:)�”}”(hjÐh]”hŒ?https://gsd.uwaterloo.ca/sites/default/files/vm-2013-berger.pdf”…”�”}”(hjãh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”jÐuh1j9hjàubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M5hjÎubeh}”(h]”j+ah ]”h"]”Œ5”ah$]”h&]”j&ajZj[uh1j h³hÊh´M5hjïh²hj\Kubj!)�”}”(hŒhttps://cados.cs.fau.de”h]”(j')�”}”(hŒ6”h]”hŒ6”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j&hjþubhÝ)�”}”(hjh]”j:)�”}”(hjh]”hŒhttps://cados.cs.fau.de”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”juh1j9hjubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M6hjþubeh}”(h]”j?ah ]”h"]”Œ6”ah$]”h&]”j:ajZj[uh1j h³hÊh´M6hjïh²hj\Kubj!)�”}”(hŒhttps://vamos.cs.fau.de”h]”(j')�”}”(hŒ7”h]”hŒ7”…”�”}”(hj2h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j&hj.ubhÝ)�”}”(hj0h]”j:)�”}”(hj0h]”hŒhttps://vamos.cs.fau.de”…”�”}”(hjCh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”j0uh1j9hj@ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M7hj.ubeh}”(h]”jSah ]”h"]”Œ7”ah$]”h&]”jNajZj[uh1j h³hÊh´M7hjïh²hj\Kubj!)�”}”(hŒhttps://undertaker.cs.fau.de”h]”(j')�”}”(hŒ8”h]”hŒ8”…”�”}”(hjbh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j&hj^ubhÝ)�”}”(hj`h]”j:)�”}”(hj`h]”hŒhttps://undertaker.cs.fau.de”…”�”}”(hjsh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”j`uh1j9hjpubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M8hj^ubeh}”(h]”jgah ]”h"]”Œ8”ah$]”h&]”jbajZj[uh1j h³hÊh´M8hjïh²hj\Kubj!)�”}”(hŒ?https://www4.cs.fau.de/Publications/2011/tartler_11_eurosys.pdf”h]”(j')�”}”(hŒ9”h]”hŒ9”…”�”}”(hj’h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j&hjŽubhÝ)�”}”(hj�h]”j:)�”}”(hj�h]”hŒ?https://www4.cs.fau.de/Publications/2011/tartler_11_eurosys.pdf”…”�”}”(hj£h²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”j�uh1j9hj ubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M9hjŽubeh}”(h]”j{ah ]”h"]”Œ9”ah$]”h&]”jvajZj[uh1j h³hÊh´M9hjïh²hj\Kubj!)�”}”(hŒ-https://paulgazzillo.com/papers/esecfse21.pdf”h]”(j')�”}”(hŒ10”h]”hŒ10”…”�”}”(hjÂh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j&hj¾ubhÝ)�”}”(hjÀh]”j:)�”}”(hjÀh]”hŒ-https://paulgazzillo.com/papers/esecfse21.pdf”…”�”}”(hjÓh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”jÀuh1j9hjÐubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M:hj¾ubeh}”(h]”j„ah ]”h"]”Œ10”ah$]”h&]”(jj´ejZj[uh1j h³hÊh´M:hjïh²hj\Kubj!)�”}”(hŒ https://github.com/paulgazz/kmax”h]”(j')�”}”(hŒ11”h]”hŒ11”…”�”}”(hjòh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”uh1j&hjîubhÝ)�”}”(hjðh]”j:)�”}”(hjðh]”hŒ https://github.com/paulgazz/kmax”…”�”}”(hjh²hh³Nh´Nubah}”(h]”h ]”h"]”h$]”h&]”Œrefuri”jðuh1j9hjubah}”(h]”h ]”h"]”h$]”h&]”uh1hÜh³hÊh´M;hjîubeh}”(h]”jÌah ]”h"]”Œ11”ah$]”h&]”jÇajZj[uh1j h³hÊh´M;hjïh²hj\Kubeh}”(h]”Œfull-sat-solver-for-kconfig”ah ]”h"]”Œfull sat solver for kconfig”ah$]”h&]”uh1hµhj] h²hh³hÊh´M"ubeh}”(h]”Œ kconfig-hints”ah ]”h"]”Œ kconfig hints”ah$]”h&]”uh1hµhh·h²hh³hÊh´M÷ubeh}”(h]”Œkconfig-language”ah ]”h"]”Œkconfig language”ah$]”h&]”uh1hµhhh²hh³hÊh´Kubeh}”(h]”h ]”h"]”h$]”h&]”Œsource”hÊuh1hŒcurrent_source”NŒ current_line”NŒsettings”Œdocutils.frontend”ŒValues”“”)�”}”(hºNŒ generator”NŒ datestamp”NŒ source_link”NŒ source_url”NŒ toc_backlinks”j¨Œfootnote_backlinks”KŒ sectnum_xform”KŒstrip_comments”NŒstrip_elements_with_classes”NŒ strip_classes”NŒ report_level”KŒ halt_level”KŒexit_status_level”KŒdebug”NŒwarning_stream”NŒ traceback”ˆŒinput_encoding”Œ utf-8-sig”Œinput_encoding_error_handler”Œstrict”Œoutput_encoding”Œutf-8”Œoutput_encoding_error_handler”jXŒerror_encoding”Œutf-8”Œerror_encoding_error_handler”Œbackslashreplace”Œ language_code”Œen”Œrecord_dependencies”NŒconfig”NŒ id_prefix”hŒauto_id_prefix”Œid”Œ dump_settings”NŒdump_internals”NŒdump_transforms”NŒdump_pseudo_xml”NŒexpose_internals”NŒstrict_visitor”NŒ_disable_config”NŒ_source”hÊŒ _destination”NŒ _config_files”]”Œ7/var/lib/git/docbuild/linux/Documentation/docutils.conf”aŒfile_insertion_enabled”ˆŒ raw_enabled”KŒline_length_limit”M'Œpep_references”NŒ pep_base_url”Œhttps://peps.python.org/”Œpep_file_url_template”Œpep-%04d”Œrfc_references”NŒ rfc_base_url”Œ&https://datatracker.ietf.org/doc/html/”Œ tab_width”KŒtrim_footnote_reference_space”‰Œsyntax_highlight”Œlong”Œ smart_quotes”ˆŒsmartquotes_locales”]”Œcharacter_level_inline_markup”‰Œdoctitle_xform”‰Œ docinfo_xform”KŒsectsubtitle_xform”‰Œ image_loading”Œlink”Œembed_stylesheet”‰Œcloak_email_addresses”ˆŒsection_self_link”‰Œenv”NubŒreporter”NŒindirect_targets”]”Œsubstitution_defs”}”Œsubstitution_names”}”Œrefnames”}”(Œ0”]”jIaŒ1”]”(jaj—jßeŒ10”]”(jujªeŒ11”]”j½aŒ2”]”jòaŒ3”]”jaŒ4”]”jaŒ5”]”jaŒ6”]”j0aŒ7”]”jDaŒ8”]”jXaŒ9”]”jlauŒrefids”}”Œnameids”}”(j3j0jjjTjQj j j1 j. jÖ jÓ jZ jW j+j(jj jujrj¸jµjßjÜjdjajjj>j;j�j~jÄjÁjöjój+j(jìjéjSjYjƒjpj³jjäjj#j jËjjûj+j+j?j[jSj‹jgj»j{jëj„jjÌuŒ nametypes”}”(j3‰j‰jT‰j ‰j1 ‰jÖ ‰jZ ‰j+‰j‰ju‰j¸‰j߉jd‰j‰j>‰j�‰jĉjö‰j+‰jì‰jSˆjƒˆj³ˆjäˆj#‰jˈjûˆj+ˆj[ˆj‹ˆj»ˆjëˆjˆuh}”(j0h·jhËjQjj jWj. j jÓ j4 jW jÙ j(j] j j| jrjjµjxjÜj»jajâjjgj;jj~jAjÁj„jójÇj(jùjéj.jSjIjkjajjuj¡j—j´jªjÇj½jéjßjüjòjjjYj"jpjVjj†jj¶j jïjjj&jj:j0jNjDjbjXjvjljjžj+jÎj?jþjSj.jgj^j{jŽj„j¾jÌjîuŒ footnote_refs”}”(j˜]”jIajš]”(jaj—jßejœ]”(jujªejž]”j½aj ]”jòaj¢]”jaj¤]”jaj¦]”jaj¨]”j0ajª]”jDaj¬]”jXaj®]”jlauŒ citation_refs”}”Œ autofootnotes”]”Œautofootnote_refs”]”Œsymbol_footnotes”]”Œsymbol_footnote_refs”]”Œ footnotes”]”(j"jVj†j¶jžjÎjþj.j^jŽj¾jîeŒ citations”]”Œautofootnote_start”KŒsymbol_footnote_start”KŒ id_counter”Œ collections”ŒCounter”“”}”jfKs…”R”Œparse_messages”]”Œtransform_messages”]”Œ transformer”NŒ include_log”]”Œ decoration”Nh²hub.