diff options
Diffstat (limited to 'poky/documentation/kernel-dev/common.rst')
| -rw-r--r-- | poky/documentation/kernel-dev/common.rst | 37 |
1 files changed, 13 insertions, 24 deletions
diff --git a/poky/documentation/kernel-dev/common.rst b/poky/documentation/kernel-dev/common.rst index fda41694dc..bd6c3fb2cf 100644 --- a/poky/documentation/kernel-dev/common.rst +++ b/poky/documentation/kernel-dev/common.rst @@ -650,13 +650,9 @@ the Broadcom 2708/2709 chipset:: KBUILD_DEFCONFIG:raspberrypi2 ?= "bcm2709_defconfig" -Aside from modifying your kernel recipe and providing your own -``defconfig`` file, you need to be sure no files or statements set -:term:`SRC_URI` to use a ``defconfig`` other than your "in-tree" file (e.g. -a kernel's ``linux-``\ `machine`\ ``.inc`` file). In other words, if the -build system detects a statement that identifies an "out-of-tree" -``defconfig`` file, that statement will override your -:term:`KBUILD_DEFCONFIG` variable. +If the build system detects a statement that identifies an "out-of-tree" +``defconfig`` file, your :term:`KBUILD_DEFCONFIG` variable will take precedence +over it. See the :term:`KBUILD_DEFCONFIG` @@ -672,7 +668,7 @@ The steps in this procedure show you how you can patch the kernel using Before attempting this procedure, be sure you have performed the steps to get ready for updating the kernel as described in the - ":ref:`kernel-dev/common:getting ready to develop using \`\`devtool\`\``" + ":ref:`kernel-dev/common:getting ready to develop using ``devtool```" section. Patching the kernel involves changing or adding configurations to an @@ -685,7 +681,7 @@ output at boot time through ``printk`` statements in the kernel's ``calibrate.c`` source code file. Applying the patch and booting the modified image causes the added messages to appear on the emulator's console. The example is a continuation of the setup procedure found in -the ":ref:`kernel-dev/common:getting ready to develop using \`\`devtool\`\``" Section. +the ":ref:`kernel-dev/common:getting ready to develop using ``devtool```" Section. #. *Check Out the Kernel Source Files:* First you must use ``devtool`` to checkout the kernel source code in its workspace. @@ -693,7 +689,7 @@ the ":ref:`kernel-dev/common:getting ready to develop using \`\`devtool\`\``" Se .. note:: See this step in the - ":ref:`kernel-dev/common:getting ready to develop using \`\`devtool\`\``" + ":ref:`kernel-dev/common:getting ready to develop using ``devtool```" section for more information. Use the following ``devtool`` command to check out the code:: @@ -804,7 +800,7 @@ the ":ref:`kernel-dev/common:getting ready to develop using \`\`devtool\`\``" Se .. note:: See Step 3 of the - ":ref:`kernel-dev/common:getting ready to develop using \`\`devtool\`\``" + ":ref:`kernel-dev/common:getting ready to develop using ``devtool```" section for information on setting up this layer. Once the command @@ -1190,7 +1186,7 @@ appear in the ``.config`` file, which is in the :term:`Build Directory`. For more information about where the ``.config`` file is located, see the example in the - ":ref:`kernel-dev/common:using \`\`menuconfig\`\``" + ":ref:`kernel-dev/common:using ``menuconfig```" section. It is simple to create a configuration fragment. One method is to use @@ -1286,7 +1282,7 @@ when you override a policy configuration in a hardware configuration fragment. In order to run this task, you must have an existing ``.config`` file. -See the ":ref:`kernel-dev/common:using \`\`menuconfig\`\``" section for +See the ":ref:`kernel-dev/common:using ``menuconfig```" section for information on how to create a configuration file. Here is sample output from the :ref:`ref-tasks-kernel_configcheck` task: @@ -1359,7 +1355,7 @@ and tasks until they produce no warnings. For more information on how to use the ``menuconfig`` tool, see the -:ref:`kernel-dev/common:using \`\`menuconfig\`\`` section. +:ref:`kernel-dev/common:using ``menuconfig``` section. Fine-Tuning the Kernel Configuration File ----------------------------------------- @@ -1562,16 +1558,9 @@ Here are some basic steps you can use to work with your own sources: changed. - :term:`PV`: The default :term:`PV` - assignment is typically adequate. It combines the - :term:`LINUX_VERSION` with the Source Control Manager (SCM) revision - as derived from the :term:`SRCPV` - variable. The combined results are a string with the following - form:: - - 3.19.11+git1+68a635bf8dfb64b02263c1ac80c948647cc76d5f_1+218bd8d2022b9852c60d32f0d770931e3cf343e2 - - While lengthy, the extra verbosity in :term:`PV` helps ensure you are - using the exact sources from which you intend to build. + assignment is typically adequate. It combines the value of + :term:`LINUX_VERSION` and the value ``+git`` which adds source control + information to :term:`PKGV` later during the packaging phase. - :term:`COMPATIBLE_MACHINE`: A list of the machines supported by your new recipe. This variable |