kernel-dev: Fixed a few links throughout manual.

The areas were found scrubbing the mega-manual.  These were minor
fixes.

(From yocto-docs rev: aaa460be3f4a446c091d66a17ca6c010f335ccc4)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark
2018-04-17 08:39:45 -07:00
committed by Richard Purdie
parent f3e5f2b6f0
commit f9f89aae51
2 changed files with 15 additions and 16 deletions

View File

@@ -64,8 +64,7 @@
<ulink url='&YOCTO_DOCS_REF_URL;#var-KMACHINE'><filename>KMACHINE</filename></ulink>
variable.
This variable is typically set to the same value as the
<ulink url='&YOCTO_DOCS_REF_URL;#var-MACHINE'><filename>MACHINE</filename></ulink>
variable, which is used by
<filename>MACHINE</filename> variable, which is used by
<ulink url='&YOCTO_DOCS_REF_URL;#bitbake-term'>BitBake</ulink>.
However, in some cases, the variable might instead refer to the
underlying platform of the <filename>MACHINE</filename>.
@@ -77,8 +76,7 @@
Multiple Corei7-based BSPs could share the same "intel-corei7-64"
value for <filename>KMACHINE</filename>.
It is important to realize that <filename>KMACHINE</filename> is
just for kernel mapping, while
<ulink url='&YOCTO_DOCS_REF_URL;#var-MACHINE'><filename>MACHINE</filename></ulink>
just for kernel mapping, while <filename>MACHINE</filename>
is the machine type within a BSP Layer.
Even with this distinction, however, these two variables can hold
the same value.
@@ -116,8 +114,7 @@
used in assembling the configuration.
If you do not specify a <filename>LINUX_KERNEL_TYPE</filename>,
it defaults to "standard".
Together with
<ulink url='&YOCTO_DOCS_REF_URL;#var-KMACHINE'><filename>KMACHINE</filename></ulink>,
Together with <filename>KMACHINE</filename>,
<filename>LINUX_KERNEL_TYPE</filename> defines the search
arguments used by the kernel tools to find the
appropriate description within the kernel Metadata with which to
@@ -644,8 +641,7 @@
aggregation concepts, and presents a detailed example using
a BSP supported by the Yocto Project (i.e. BeagleBone Board).
For complete information on BSP layer file hierarchy, see the
<ulink url='&YOCTO_DOCS_BSP_URL;'>Yocto Project Board Support
Package (BSP) Developer's Guide</ulink>.
<ulink url='&YOCTO_DOCS_BSP_URL;'>Yocto Project Board Support Package (BSP) Developer's Guide</ulink>.
</para>
<section id='bsp-description-file-overview'>
@@ -856,7 +852,7 @@
<para>
Now consider the "minnow" description for the "tiny" kernel
type (i.e. <filename>minnow-tiny.scc</filename>:
type (i.e. <filename>minnow-tiny.scc</filename>):
<literallayout class='monospaced'>
define KMACHINE minnow
define KTYPE tiny
@@ -1018,8 +1014,7 @@
<para>
If you modify the Metadata, you must not forget to update the
<ulink url='&YOCTO_DOCS_REF_URL;#var-SRCREV'><filename>SRCREV</filename></ulink>
statements in the kernel's recipe.
<filename>SRCREV</filename> statements in the kernel's recipe.
In particular, you need to update the
<filename>SRCREV_meta</filename> variable to match the commit in
the <filename>KMETA</filename> branch you wish to use.
@@ -1227,9 +1222,13 @@
</para></listitem>
<listitem><para>
<filename>define</filename>:
Defines variables, such as <filename>KMACHINE</filename>,
<filename>KTYPE</filename>, <filename>KARCH</filename>,
and <filename>KFEATURE_DESCRIPTION</filename>.</para></listitem>
Defines variables, such as
<ulink url='&YOCTO_DOCS_REF_URL;#var-KMACHINE'><filename>KMACHINE</filename></ulink>,
<ulink url='&YOCTO_DOCS_REF_URL;#var-KTYPE'><filename>KTYPE</filename></ulink>,
<ulink url='&YOCTO_DOCS_REF_URL;#var-KARCH'><filename>KARCH</filename></ulink>,
and
<ulink url='&YOCTO_DOCS_REF_URL;#var-KFEATURE_DESCRIPTION'><filename>KFEATURE_DESCRIPTION</filename></ulink>.
</para></listitem>
<listitem><para>
<filename>include SCC_FILE</filename>:
Includes an SCC file in the current file.