From: "Jamaluddin, Khairul Rohaizzat" <khairul.rohaizzat.jamaluddin@intel.com>
To: "docs@lists.yoctoproject.org" <docs@lists.yoctoproject.org>
Subject: Re: [PATCH v3] sphinx: ref-variables: Added entry for IMAGE_EFI_BOOT_FILES
Date: Mon, 28 Sep 2020 02:39:23 +0000 [thread overview]
Message-ID: <DM5PR11MB1993C7F06445E9E4E8A8F684DE350@DM5PR11MB1993.namprd11.prod.outlook.com> (raw)
In-Reply-To: <1600687615-18331-1-git-send-email-khairul.rohaizzat.jamaluddin@intel.com>
Hi,
Does anyone have any updates on this patch? Does it pass for merge?
Thank you & Kind regards,
Khairul
-----Original Message-----
From: Jamaluddin, Khairul Rohaizzat <khairul.rohaizzat.jamaluddin@intel.com>
Sent: Monday, September 21, 2020 7:27 PM
To: docs@lists.yoctoproject.org
Cc: Jamaluddin, Khairul Rohaizzat <khairul.rohaizzat.jamaluddin@intel.com>
Subject: [PATCH v3] sphinx: ref-variables: Added entry for IMAGE_EFI_BOOT_FILES
From: Khairul Rohaizzat Jamaluddin <khairul.rohaizzat.jamaluddin@intel.com>
IMAGE_EFI_BOOT_FILES created to help differentiate files needed between bootimg-efi and bootimg-partition when creating the installer/.wic file.
Signed-off-by: Khairul Rohaizzat Jamaluddin <khairul.rohaizzat.jamaluddin@intel.com>
---
documentation/ref-manual/ref-variables.rst | 38 +++++++++++++++++++++++++++++-
1 file changed, 37 insertions(+), 1 deletion(-)
diff --git a/documentation/ref-manual/ref-variables.rst b/documentation/ref-manual/ref-variables.rst
index 625a37c..c09809e 100644
--- a/documentation/ref-manual/ref-variables.rst
+++ b/documentation/ref-manual/ref-variables.rst
@@ -2902,10 +2902,46 @@ system and gives an overview of their function and contents.
The base name of image output files. This variable defaults to the
recipe name (``${``\ :term:`PN`\ ``}``).
+ IMAGE_EFI_BOOT_FILES
+ A space-separated list of files installed into the boot partition
+ when preparing an image using the Wic tool with the
+ ``bootimg-efi`` source plugin. By default,
+ the files are
+ installed under the same name as the source files. To change the
+ installed name, separate it from the original name with a semi-colon
+ (;). Source files need to be located in
+ :term:`DEPLOY_DIR_IMAGE`. Here are two
+ examples:
+ ::
+
+ IMAGE_EFI_BOOT_FILES = "${KERNEL_IMAGETYPE};bz2"
+ IMAGE_EFI_BOOT_FILES = "${KERNEL_IMAGETYPE} microcode.cpio"
+
+ Alternatively, source files can be picked up using a glob pattern. In
+ this case, the destination file must have the same name as the base
+ name of the source file path. To install files into a directory
+ within the target location, pass its name after a semi-colon (;).
+ Here are two examples:
+ ::
+
+ IMAGE_EFI_BOOT_FILES = "boot/loader/*"
+ IMAGE_EFI_BOOT_FILES = "boot/loader/*;boot/"
+
+ The first example
+ installs all files from ``${DEPLOY_DIR_IMAGE}/boot/loader/``
+ into the root of the target partition. The second example installs
+ the same files into a ``boot`` directory within the target partition.
+
+ You can find information on how to use the Wic tool in the
+ ":ref:`dev-manual/dev-manual-common-tasks:creating partitioned images using wic`"
+ section of the Yocto Project Development Tasks Manual. Reference
+ material for Wic is located in the
+ ":doc:`../ref-manual/ref-kickstart`" chapter.
+
IMAGE_BOOT_FILES
A space-separated list of files installed into the boot partition
when preparing an image using the Wic tool with the
- ``bootimg-partition`` or ``bootimg-efi`` source plugin. By default,
+ ``bootimg-partition`` source plugin. By default,
the files are
installed under the same name as the source files. To change the
installed name, separate it from the original name with a semi-colon
--
2.7.4
next prev parent reply other threads:[~2020-09-28 2:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 11:26 [PATCH v3] sphinx: ref-variables: Added entry for IMAGE_EFI_BOOT_FILES Jamaluddin, Khairul Rohaizzat
2020-09-28 2:39 ` Jamaluddin, Khairul Rohaizzat [this message]
2020-09-29 22:30 ` [docs] " Richard Purdie
2020-09-30 2:22 ` Jamaluddin, Khairul Rohaizzat
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=DM5PR11MB1993C7F06445E9E4E8A8F684DE350@DM5PR11MB1993.namprd11.prod.outlook.com \
--to=khairul.rohaizzat.jamaluddin@intel.com \
--cc=docs@lists.yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.