mirrors/poky
1
0
Fork 0
mirror of https://git.yoctoproject.org/poky synced 2026-04-05 08:02:25 +02:00
Code Issues Packages Projects Releases Wiki Activity

sphinx: kernel-dev: add figures

Browse Source 
(From yocto-docs rev: cd859cca2e6861fbb5bac68c2f6e972285c47dcb)

Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Nicolas Dechesne
2020-07-29 09:55:43 +02:00
committed by Richard Purdie
parent 0640f19206
commit ffa58f2985
2 changed files with 9 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
documentation/kernel-dev/kernel-dev-concepts-appx.rst
View File

@@ -224,6 +224,9 @@ the line-by-line code ``diff`` level is now a trivial operation.
The following illustration shows the conceptual Yocto Linux kernel.
.. image:: figures/kernel-architecture-overview.png
:align: center
In the illustration, the "Kernel.org Branch Point" marks the specific
spot (or Linux kernel release) from which the Yocto Linux kernel is
created. From this point forward in the tree, features and differences
@@ -324,6 +327,9 @@ host system when you build the kernel using Bitbake. This
:term:`Build Directory` contains all the
source files used during the build.
.. image:: figures/kernel-overview-2-generic.png
:align: center
Again, for additional information on the Yocto Project kernel's
architecture and its branching strategy, see the "`Yocto Linux Kernel
Architecture and Branching

3
documentation/kernel-dev/kernel-dev-intro.rst
View File

@@ -110,6 +110,9 @@ This section presents a high-level overview of the Yocto Project kernel
modification workflow. The illustration and accompanying list provide
general information and references for further information.
.. image:: figures/kernel-dev-flow.png
:align: center
1. *Set up Your Host Development System to Support Development Using the
Yocto Project*: See the "`Setting Up the Development Host to Use the
Yocto Project <&YOCTO_DOCS_DEV_URL;#dev-manual-start>`__" section in