summaryrefslogtreecommitdiffstats
path: root/documentation/kernel-dev/intro.rst
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/kernel-dev/intro.rst')
-rw-r--r--documentation/kernel-dev/intro.rst10
1 files changed, 5 insertions, 5 deletions
diff --git a/documentation/kernel-dev/intro.rst b/documentation/kernel-dev/intro.rst
index 06cc884386..a663733a1d 100644
--- a/documentation/kernel-dev/intro.rst
+++ b/documentation/kernel-dev/intro.rst
@@ -108,12 +108,12 @@ general information and references for further information.
108.. image:: figures/kernel-dev-flow.png 108.. image:: figures/kernel-dev-flow.png
109 :width: 100% 109 :width: 100%
110 110
1111. *Set up Your Host Development System to Support Development Using the 111#. *Set up Your Host Development System to Support Development Using the
112 Yocto Project*: See the ":doc:`/dev-manual/start`" section in 112 Yocto Project*: See the ":doc:`/dev-manual/start`" section in
113 the Yocto Project Development Tasks Manual for options on how to get 113 the Yocto Project Development Tasks Manual for options on how to get
114 a build host ready to use the Yocto Project. 114 a build host ready to use the Yocto Project.
115 115
1162. *Set Up Your Host Development System for Kernel Development:* It is 116#. *Set Up Your Host Development System for Kernel Development:* It is
117 recommended that you use ``devtool`` for kernel 117 recommended that you use ``devtool`` for kernel
118 development. Alternatively, you can use traditional kernel 118 development. Alternatively, you can use traditional kernel
119 development methods with the Yocto Project. Either way, there are 119 development methods with the Yocto Project. Either way, there are
@@ -131,7 +131,7 @@ general information and references for further information.
131 ":ref:`kernel-dev/common:getting ready for traditional kernel development`" 131 ":ref:`kernel-dev/common:getting ready for traditional kernel development`"
132 section. 132 section.
133 133
1343. *Make Changes to the Kernel Source Code if applicable:* Modifying the 134#. *Make Changes to the Kernel Source Code if applicable:* Modifying the
135 kernel does not always mean directly changing source files. However, 135 kernel does not always mean directly changing source files. However,
136 if you have to do this, you make the changes to the files in the 136 if you have to do this, you make the changes to the files in the
137 Yocto's :term:`Build Directory` if you are using ``devtool``. For more 137 Yocto's :term:`Build Directory` if you are using ``devtool``. For more
@@ -144,7 +144,7 @@ general information and references for further information.
144 ":ref:`kernel-dev/common:using traditional kernel development to patch the kernel`" 144 ":ref:`kernel-dev/common:using traditional kernel development to patch the kernel`"
145 section. 145 section.
146 146
1474. *Make Kernel Configuration Changes if Applicable:* If your situation 147#. *Make Kernel Configuration Changes if Applicable:* If your situation
148 calls for changing the kernel's configuration, you can use 148 calls for changing the kernel's configuration, you can use
149 :ref:`menuconfig <kernel-dev/common:using \`\`menuconfig\`\`>`, 149 :ref:`menuconfig <kernel-dev/common:using \`\`menuconfig\`\`>`,
150 which allows you to 150 which allows you to
@@ -169,7 +169,7 @@ general information and references for further information.
169 Additionally, if you are working in a BSP layer and need to modify 169 Additionally, if you are working in a BSP layer and need to modify
170 the BSP's kernel's configuration, you can use ``menuconfig``. 170 the BSP's kernel's configuration, you can use ``menuconfig``.
171 171
1725. *Rebuild the Kernel Image With Your Changes:* Rebuilding the kernel 172#. *Rebuild the Kernel Image With Your Changes:* Rebuilding the kernel
173 image applies your changes. Depending on your target hardware, you 173 image applies your changes. Depending on your target hardware, you
174 can verify your changes on actual hardware or perhaps QEMU. 174 can verify your changes on actual hardware or perhaps QEMU.
175 175