diff options
author | Alexander Kanavin <alex.kanavin@gmail.com> | 2022-08-02 10:38:02 +0200 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2022-08-12 23:11:28 +0100 |
commit | ea613c8f70d5e87a6327d52d935b8646a8fe3077 (patch) | |
tree | 015de6c5b2459fe8a2c11cb6dcea3ad14fca8c9f /documentation/kernel-dev/intro.rst | |
parent | f7763317f8f9844e325101fde1eac6ecd8cfdbee (diff) | |
download | poky-ea613c8f70d5e87a6327d52d935b8646a8fe3077.tar.gz |
kernel-dev: working with kernel using devtool does not require building and installing eSDK
In fact, all the same tasks can be done directly from a Yocto build. Let's just
drop the steps to produce and install the eSDK - if someone wants it, the SDK
manual covers everything.
(From yocto-docs rev: 582aa6a8e461bbd698b121403dcd25ddb563a464)
Signed-off-by: Alexander Kanavin <alex@linutronix.de>
Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/kernel-dev/intro.rst')
-rw-r--r-- | documentation/kernel-dev/intro.rst | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/documentation/kernel-dev/intro.rst b/documentation/kernel-dev/intro.rst index b9ce7f241c..4ff4dc7d35 100644 --- a/documentation/kernel-dev/intro.rst +++ b/documentation/kernel-dev/intro.rst | |||
@@ -114,13 +114,13 @@ general information and references for further information. | |||
114 | a build host ready to use the Yocto Project. | 114 | a build host ready to use the Yocto Project. |
115 | 115 | ||
116 | 2. *Set Up Your Host Development System for Kernel Development:* It is | 116 | 2. *Set Up Your Host Development System for Kernel Development:* It is |
117 | recommended that you use ``devtool`` and an extensible SDK 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 |
120 | steps you need to take to get the development environment ready. | 120 | steps you need to take to get the development environment ready. |
121 | 121 | ||
122 | Using ``devtool`` and the eSDK requires that you have a clean build | 122 | Using ``devtool`` requires that you have a clean build |
123 | of the image and that you are set up with the appropriate eSDK. For | 123 | of the image. For |
124 | more information, see the | 124 | more information, see the |
125 | ":ref:`kernel-dev/common:getting ready to develop using \`\`devtool\`\``" | 125 | ":ref:`kernel-dev/common:getting ready to develop using \`\`devtool\`\``" |
126 | section. | 126 | section. |
@@ -134,7 +134,7 @@ general information and references for further information. | |||
134 | 3. *Make Changes to the Kernel Source Code if applicable:* Modifying the | 134 | 3. *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 | eSDK's Build Directory if you are using ``devtool``. For more | 137 | Yocto's Build Directory if you are using ``devtool``. For more |
138 | information, see the | 138 | information, see the |
139 | ":ref:`kernel-dev/common:using \`\`devtool\`\` to patch the kernel`" | 139 | ":ref:`kernel-dev/common:using \`\`devtool\`\` to patch the kernel`" |
140 | section. | 140 | section. |