From: Scott Rifenbark Date: Mon, 2 Jan 2017 21:29:31 +0000 (-0800) Subject: dev-manual: Updated "Building an Initial RAM Filesystem (initramfs) Image" section X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=1b3d0e516819d0ab3b4a3c0c5163db610f0d3f95;p=thirdparty%2Fopenembedded%2Fopenembedded-core-contrib.git dev-manual: Updated "Building an Initial RAM Filesystem (initramfs) Image" section Fixes [YOCTO #7096] Applied a couple review comments to the section to clarify where to set key variables. Also fixed an incorrect variable name used to specify the *.cpio file. (From yocto-docs rev: 1ef9bb89057be46878a70c558268b5ace43967f8) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml index 49d8f5c10c0..b2a2e32c5d2 100644 --- a/documentation/dev-manual/dev-manual-common-tasks.xml +++ b/documentation/dev-manual/dev-manual-common-tasks.xml @@ -5489,17 +5489,18 @@ To build an initramfs image and bundle it into the kernel, set the - following variables: + INITRAMFS_IMAGE_BUNDLE + variable in your local.conf file, and set the + INITRAMFS_IMAGE + variable in your machine.conf file: INITRAMFS_IMAGE_BUNDLE = "1" INITRAMFS_IMAGE = "image_recipe_name" - Setting the - INITRAMFS_IMAGE_BUNDLE - flag causes the initramfs created by the recipe - and defined by - INITRAMFS_IMAGE - to be unpacked into the ${B}/usr/ directory. + Setting the INITRAMFS_IMAGE_BUNDLE + flag causes the initramfs created by the recipe and defined by + INITRAMFS_IMAGE to be unpacked into the + ${B}/usr/ directory. The unpacked initramfs is then passed to the kernel's Makefile using the CONFIG_INITRAMFS_SOURCE @@ -5528,7 +5529,7 @@ .cpio.xz file. You can ensure you produce one of these .cpio.* files by setting the - IMAGE_FSTYPES + INITRAMFS_FSTYPES variable in your configuration file to one or more of the above file types.