diff options
Diffstat (limited to 'poky/documentation')
-rw-r--r-- | poky/documentation/bsp-guide/bsp.rst | 10 | ||||
-rw-r--r-- | poky/documentation/dev-manual/common-tasks.rst | 2 | ||||
-rw-r--r-- | poky/documentation/ref-manual/terms.rst | 4 | ||||
-rw-r--r-- | poky/documentation/ref-manual/variables.rst | 2 |
4 files changed, 9 insertions, 9 deletions
diff --git a/poky/documentation/bsp-guide/bsp.rst b/poky/documentation/bsp-guide/bsp.rst index b80354a05b..65652ff898 100644 --- a/poky/documentation/bsp-guide/bsp.rst +++ b/poky/documentation/bsp-guide/bsp.rst @@ -1011,9 +1011,9 @@ If you plan on customizing a recipe for a particular BSP, you need to do the following: - Create a ``*.bbappend`` file for the modified recipe. For information on using - append files, see the ":ref:`dev-manual/common-tasks:using - .bbappend files in your layer`" section in the Yocto Project Development - Tasks Manual. + append files, see the + ":ref:`dev-manual/common-tasks:appending other layers metadata with your layer`" + section in the Yocto Project Development Tasks Manual. - Ensure your directory structure in the BSP layer that supports your machine is such that the OpenEmbedded build system can find it. See @@ -1266,7 +1266,7 @@ located in the layer ``poky/meta-yocto-bsp/conf/machine`` and is named EXTRA_IMAGEDEPENDS += "u-boot" DEFAULTTUNE ?= "cortexa8hf-neon" - include conf/machine/include/tune-cortexa8.inc + include conf/machine/include/arm/armv7a/tune-cortexa8.inc IMAGE_FSTYPES += "tar.bz2 jffs2 wic wic.bmap" EXTRA_IMAGECMD:jffs2 = "-lnp " @@ -1344,7 +1344,7 @@ Project Reference Manual. .. note:: The include statement that pulls in the - ``conf/machine/include/tune-cortexa8.inc`` file provides many tuning + ``conf/machine/include/arm/tune-cortexa8.inc`` file provides many tuning possibilities. - :term:`IMAGE_FSTYPES`: The diff --git a/poky/documentation/dev-manual/common-tasks.rst b/poky/documentation/dev-manual/common-tasks.rst index 7f51674a92..4a5011ea74 100644 --- a/poky/documentation/dev-manual/common-tasks.rst +++ b/poky/documentation/dev-manual/common-tasks.rst @@ -2064,7 +2064,7 @@ Now comes the time to actually build an image and you need a kernel recipe, but which one? You can configure your build to call out the kernel recipe you want by using the :term:`PREFERRED_PROVIDER` variable. As an example, consider the :yocto_git:`x86-base.inc -</poky/tree/meta/conf/machine/include/x86-base.inc>` include file, which is a +</poky/tree/meta/conf/machine/include/x86/x86-base.inc>` include file, which is a machine (i.e. :term:`MACHINE`) configuration file. This include file is the reason all x86-based machines use the ``linux-yocto`` kernel. Here are the relevant lines from the include file:: diff --git a/poky/documentation/ref-manual/terms.rst b/poky/documentation/ref-manual/terms.rst index 54469e507d..32658051a5 100644 --- a/poky/documentation/ref-manual/terms.rst +++ b/poky/documentation/ref-manual/terms.rst @@ -21,8 +21,8 @@ universal, the list includes them just in case: Information in append files extends or overrides the information in the similarly-named recipe file. For an example of an append file in use, see - the ":ref:`dev-manual/common-tasks:Using .bbappend Files in - Your Layer`" section in the Yocto Project Development Tasks Manual. + the ":ref:`dev-manual/common-tasks:appending other layers metadata with your layer`" + section in the Yocto Project Development Tasks Manual. When you name an append file, you can use the "``%``" wildcard character to allow for matching recipe names. For example, suppose you have an diff --git a/poky/documentation/ref-manual/variables.rst b/poky/documentation/ref-manual/variables.rst index 7aecda0174..d5ac1926b6 100644 --- a/poky/documentation/ref-manual/variables.rst +++ b/poky/documentation/ref-manual/variables.rst @@ -8256,7 +8256,7 @@ system and gives an overview of their function and contents. These tune-specific package architectures are defined in the machine include files. Here is an example of the "core2-32" tuning as used in - the ``meta/conf/machine/include/tune-core2.inc`` file:: + the ``meta/conf/machine/include/x86/tune-core2.inc`` file:: TUNE_PKGARCH:tune-core2-32 = "core2-32" |