From 453a619dc692d1a085ef98e0ccda3eed58f0b8a0 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Tue, 3 Oct 2017 14:36:50 -0700 Subject: kernel-dev: Updated lists for formatting consistency (From yocto-docs rev: 7fe10c067219eccdbfd8d99223cdb38b84d7d2a5) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/kernel-dev/kernel-dev-common.xml | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) (limited to 'documentation') diff --git a/documentation/kernel-dev/kernel-dev-common.xml b/documentation/kernel-dev/kernel-dev-common.xml index 2b47eafac8..3dd4cd88b6 100644 --- a/documentation/kernel-dev/kernel-dev-common.xml +++ b/documentation/kernel-dev/kernel-dev-common.xml @@ -2726,7 +2726,8 @@ The OpenEmbedded build system searches all forms of kernel Metadata on the SRC_URI statement regardless of whether the Metadata is in the "kernel-cache", system kernel - Metadata, or a recipe-space Metadata. + Metadata, or a recipe-space Metadata (i.e. part of the kernel + recipe). See the "Kernel Metadata Location" section for additional information. @@ -2749,6 +2750,7 @@ to the build. + Create the Feature File: Create a .scc file and locate it just as you would any other patch file, .cfg file, or fetcher item @@ -2791,6 +2793,7 @@ test.cfg. + Add the Feature File to SRC_URI: Add the .scc file to the recipe's SRC_URI statement: @@ -2800,7 +2803,9 @@ path is appended to the existing path. - Specify the feature as a kernel feature: + Specify the Feature as a Kernel Feature: + Use the KERNEL_FEATURES statement + to specify the feature as a kernel feature: KERNEL_FEATURES_append = " test.scc" -- cgit v1.2.3-54-g00ecf