From: "Jon Mason" <jdmason@kudzu.us>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH v2 3/3] docs: update docs with new tune locations
Date: Mon, 16 Aug 2021 18:01:44 -0400 [thread overview]
Message-ID: <20210816220144.26018-4-jdmason@kudzu.us> (raw)
In-Reply-To: <20210816220144.26018-1-jdmason@kudzu.us>
Signed-off-by: Jon Mason <jdmason@kudzu.us>
---
documentation/bsp-guide/bsp.rst | 4 ++--
documentation/dev-manual/common-tasks.rst | 2 +-
documentation/ref-manual/variables.rst | 2 +-
3 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/documentation/bsp-guide/bsp.rst b/documentation/bsp-guide/bsp.rst
index b80354a05bb6..37b052427e62 100644
--- a/documentation/bsp-guide/bsp.rst
+++ b/documentation/bsp-guide/bsp.rst
@@ -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/documentation/dev-manual/common-tasks.rst b/documentation/dev-manual/common-tasks.rst
index 7f51674a92a3..4a5011ea749a 100644
--- a/documentation/dev-manual/common-tasks.rst
+++ b/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/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
index 7aecda017454..d5ac1926b6ee 100644
--- a/documentation/ref-manual/variables.rst
+++ b/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"
--
2.20.1
next prev parent reply other threads:[~2021-08-16 22:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-16 22:01 [PATCH v2 0/3] tunes: the great migration Jon Mason
2021-08-16 22:01 ` [PATCH v2 1/3] conf/machine: move tune files to architecture directories Jon Mason
2021-08-16 22:01 ` [PATCH v2 2/3] yocto-bsp: update machine confs with new tune locations Jon Mason
2021-08-16 22:01 ` Jon Mason [this message]
2021-08-17 20:44 ` [OE-core] [PATCH v2 0/3] tunes: the great migration Alexandre Belloni
2021-08-18 0:58 ` Jon Mason
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210816220144.26018-4-jdmason@kudzu.us \
--to=jdmason@kudzu.us \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox