diff options
Diffstat (limited to 'documentation/kernel-dev/advanced.rst')
| -rw-r--r-- | documentation/kernel-dev/advanced.rst | 49 |
1 files changed, 21 insertions, 28 deletions
diff --git a/documentation/kernel-dev/advanced.rst b/documentation/kernel-dev/advanced.rst index b16b3e0517..4c463503f6 100644 --- a/documentation/kernel-dev/advanced.rst +++ b/documentation/kernel-dev/advanced.rst @@ -69,8 +69,7 @@ to indicate the branch. You can use the :term:`KBRANCH` value to define an alternate branch typically with a machine override as shown here from the ``meta-yocto-bsp`` layer:: - KBRANCH:edgerouter = "standard/edgerouter" - + KBRANCH:beaglebone-yocto = "standard/beaglebone" The linux-yocto style recipes can optionally define the following variables: @@ -304,8 +303,8 @@ The following listings show the ``build.scc`` file and part of the . . . - char *dump_write = NULL, *files_source = NULL; - int opt; + char *dump_write = NULL, *files_source = NULL; + int opt; -- 2.10.1 @@ -352,17 +351,15 @@ in the manual. Kernel Types ------------ -A kernel type defines a high-level kernel policy by aggregating -non-hardware configuration fragments with patches you want to use when -building a Linux kernel of a specific type (e.g. a real-time kernel). -Syntactically, kernel types are no different than features as described -in the ":ref:`kernel-dev/advanced:features`" section. The -:term:`LINUX_KERNEL_TYPE` -variable in the kernel recipe selects the kernel type. For example, in -the ``linux-yocto_4.12.bb`` kernel recipe found in -``poky/meta/recipes-kernel/linux``, a -:ref:`require <bitbake:bitbake-user-manual/bitbake-user-manual-metadata:\`\`require\`\` directive>` directive -includes the ``poky/meta/recipes-kernel/linux/linux-yocto.inc`` file, +A kernel type defines a high-level kernel policy by aggregating non-hardware +configuration fragments with patches you want to use when building a Linux +kernel of a specific type (e.g. a real-time kernel). Syntactically, kernel +types are no different than features as described in the +":ref:`kernel-dev/advanced:features`" section. The :term:`LINUX_KERNEL_TYPE` +variable in the kernel recipe selects the kernel type. For example, in the +``linux-yocto_4.12.bb`` kernel recipe found in ``poky/meta/recipes-kernel/linux``, a +:ref:`require <bitbake-user-manual/bitbake-user-manual-metadata:\`\`require\`\` directive>` +directive includes the ``poky/meta/recipes-kernel/linux/linux-yocto.inc`` file, which has the following statement that defines the default kernel type:: LINUX_KERNEL_TYPE ??= "standard" @@ -566,15 +563,7 @@ Example Many real-world examples are more complex. Like any other ``.scc`` file, BSP descriptions can aggregate features. Consider the Minnow BSP definition given the ``linux-yocto-4.4`` branch of the -``yocto-kernel-cache`` (i.e. -``yocto-kernel-cache/bsp/minnow/minnow.scc``): - -.. note:: - - Although the Minnow Board BSP is unused, the Metadata remains and is - being used here just as an example. - -:: +``yocto-kernel-cache`` (i.e. ``yocto-kernel-cache/bsp/minnow/minnow.scc``):: include cfg/x86.scc include features/eg20t/eg20t.scc @@ -597,6 +586,11 @@ definition given the ``linux-yocto-4.4`` branch of the kconf hardware minnow.cfg kconf hardware minnow-dev.cfg +.. note:: + + Although the Minnow Board BSP is unused, the Metadata remains and is + being used here just as an example. + The ``minnow.scc`` description file includes a hardware configuration fragment (``minnow.cfg``) specific to the Minnow BSP as well as several more general configuration fragments and features enabling hardware @@ -735,11 +729,10 @@ reside in a separate repository. The OpenEmbedded build system adds the Metadata to the build as a "type=kmeta" repository through the :term:`SRC_URI` variable. As an example, consider the following :term:`SRC_URI` statement from the -``linux-yocto_4.12.bb`` kernel recipe:: - - SRC_URI = "git://git.yoctoproject.org/linux-yocto-4.12.git;name=machine;branch=${KBRANCH}; \ - git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-4.12;destsuffix=${KMETA}" +``linux-yocto_5.15.bb`` kernel recipe:: + SRC_URI = "git://git.yoctoproject.org/linux-yocto.git;name=machine;branch=${KBRANCH};protocol=https \ + git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-5.15;destsuffix=${KMETA};protocol=https" ``${KMETA}``, in this context, is simply used to name the directory into which the Git fetcher places the Metadata. This behavior is no different |