diff options
-rw-r--r-- | documentation/kernel-dev/kernel-dev-advanced.xml | 22 |
1 files changed, 11 insertions, 11 deletions
diff --git a/documentation/kernel-dev/kernel-dev-advanced.xml b/documentation/kernel-dev/kernel-dev-advanced.xml index 12d3d7c8ec..879d3f285a 100644 --- a/documentation/kernel-dev/kernel-dev-advanced.xml +++ b/documentation/kernel-dev/kernel-dev-advanced.xml | |||
@@ -849,17 +849,14 @@ The description file can include multiple patch statements, one per patch. | |||
849 | <title>Features</title> | 849 | <title>Features</title> |
850 | 850 | ||
851 | <para> | 851 | <para> |
852 | Features are a combination of configuration fragments and patches. | 852 | Features are complex kernel Metadata types that consist |
853 | Or, more accurately, configuration fragments and patches are | 853 | of configuration fragments (<filename>kconf</filename>), patches |
854 | simple forms of a feature, which is a more complex metadata type. | 854 | (<filename>patch</filename>), and possibly other feature |
855 | In addition to the <filename>kconf</filename> and | 855 | description files (<filename>include</filename>). |
856 | <filename>patch</filename> commands, features often aggregate | ||
857 | description files with the <filename>include</filename> command. | ||
858 | </para> | 856 | </para> |
859 | 857 | ||
860 | <para> | 858 | <para> |
861 | A hypothetical example of a feature description file might look | 859 | Here is an example that shows a feature description file: |
862 | like the following: | ||
863 | <literallayout class='monospaced'> | 860 | <literallayout class='monospaced'> |
864 | features/myfeature.scc | 861 | features/myfeature.scc |
865 | define KFEATURE_DESCRIPTION "Enable myfeature" | 862 | define KFEATURE_DESCRIPTION "Enable myfeature" |
@@ -870,12 +867,15 @@ The description file can include multiple patch statements, one per patch. | |||
870 | include cfg/myfeature_dependency.scc | 867 | include cfg/myfeature_dependency.scc |
871 | kconf non-hardware myfeature.cfg | 868 | kconf non-hardware myfeature.cfg |
872 | </literallayout> | 869 | </literallayout> |
870 | This example shows how the <filename>patch</filename> and | ||
871 | <filename>kconf</filename> commands are used as well as | ||
872 | how an additional feature description file is included. | ||
873 | </para> | 873 | </para> |
874 | 874 | ||
875 | <para> | 875 | <para> |
876 | Features are typically less granular than configuration | 876 | Typically, features are less granular than configuration |
877 | fragments and are more likely than configurations fragments | 877 | fragments and are more likely than configuration fragments |
878 | and patches to be the types of things you will want to specify | 878 | and patches to be the types of things you want to specify |
879 | in the <filename>KERNEL_FEATURES</filename> variable of the | 879 | in the <filename>KERNEL_FEATURES</filename> variable of the |
880 | Linux kernel recipe. | 880 | Linux kernel recipe. |
881 | See the "<link linkend='using-kernel-metadata-in-a-recipe'>Using Kernel Metadata in a Recipe</link>" | 881 | See the "<link linkend='using-kernel-metadata-in-a-recipe'>Using Kernel Metadata in a Recipe</link>" |