Well I'm in Daisy and I can see that variable, so I think that the
documentation is out of date :)
[geckos@csi24 yocto-daisy]$ find sources/ -name "*.bb*" -exec grep
--color -H INITRD_IMAGE {} \;
sources/poky/meta/recipes-extended/images/core-image-testmaster.bb:INITRD_IMAGE
= "core-image-testmaster-initramfs"
sources/poky/meta/classes/image-live.bbclass:INITRD_IMAGE ?=
"core-image-minimal-initramfs"
sources/poky/meta/classes/image-live.bbclass:INITRD ?=
"${DEPLOY_DIR_IMAGE}/${INITRD_IMAGE}-${MACHINE}.cpio.gz"
sources/poky/meta/classes/image-live.bbclass:do_bootimg[depends] +=
"${INITRD_IMAGE}:do_rootfs"
[geckos@csi24 yocto-daisy]$
2016-06-22 7:03 GMT-03:00 Robert P. J. Day <[email protected]>:
>
> (asked about this on the OE list recently, but no response, so i'll
> harass this list.)
>
> poking around initramfs content and recipes, and noticed this in the
> latest poky checkout:
>
> $ grep -rw INITRD_IMAGE *
> documentation/ref-manual/ref-variables.xml: <glossentry
> id='var-INITRD_IMAGE'><glossterm>INITRD_IMAGE</glossterm>
> documentation/ref-manual/ref-variables.xml: INITRD_IMAGE[doc]
> = "When building a "live" bootable image (i.e. when IMAGE_FSTYPES contains
> "live"), INITRD_IMAGE specifies the image recipe that should be built to
> provide the initial RAM disk image."
> documentation/ref-manual/ref-variables.xml: contains
> "live"), <filename>INITRD_IMAGE</filename>
> meta/recipes-extended/images/core-image-testmaster.bb:INITRD_IMAGE =
> "core-image-testmaster-initramfs"
> $
>
> so ... a bit of documentation on the alleged variable INITRD_IMAGE,
> and a single assignment, and no usage.
>
> but if i drop the requirement that it be a word:
>
> $ grep -r INITRD_IMAGE *
> documentation/ref-manual/ref-variables.xml: <glossentry
> id='var-INITRD_IMAGE'><glossterm>INITRD_IMAGE</glossterm>
> documentation/ref-manual/ref-variables.xml: INITRD_IMAGE[doc]
> = "When building a "live" bootable image (i.e. when IMAGE_FSTYPES contains
> "live"), INITRD_IMAGE specifies the image recipe that should be built to
> provide the initial RAM disk image."
> documentation/ref-manual/ref-variables.xml: contains
> "live"), <filename>INITRD_IMAGE</filename>
> meta/recipes-extended/images/core-image-testmaster.bb:INITRD_IMAGE =
> "core-image-testmaster-initramfs"
> meta/classes/image-vm.bbclass:# Using an initramfs is optional. Enable it by
> setting INITRD_IMAGE_VM.
> meta/classes/image-vm.bbclass:INITRD_IMAGE_VM ?= ""
> meta/classes/image-vm.bbclass:INITRD_VM ?=
> "${@'${DEPLOY_DIR_IMAGE}/${INITRD_IMAGE_VM}-${MACHINE}.cpio.gz' if
> '${INITRD_IMAGE_VM}' else ''}"
> meta/classes/image-vm.bbclass:do_bootdirectdisk[depends] +=
> "${@'${INITRD_IMAGE_VM}:do_image_complete' if '${INITRD_IMAGE_VM}' else ''}"
> meta/classes/image-live.bbclass:INITRD_IMAGE_LIVE ?=
> "core-image-minimal-initramfs"
> meta/classes/image-live.bbclass:INITRD_LIVE ?=
> "${DEPLOY_DIR_IMAGE}/${INITRD_IMAGE_LIVE}-${MACHINE}.cpio.gz"
> meta/classes/image-live.bbclass: initrd_i = d.getVar('INITRD_IMAGE_LIVE',
> True)
> meta/classes/image-live.bbclass: bb.error('INITRD_IMAGE_LIVE %s cannot
> use image live, hddimg or iso.' % initrd_i)
> $
>
> suddenly, i see references to "INITRD_IMAGE_VM" and
> "INITRD_IMAGE_LIVE". so is "INITRD_IMAGE" correct? i don't see how
> that makes sense unless "VM" and "LIVE" are some weird form of
> override.
>
> thoughts?
>
> rday
>
> --
>
> ========================================================================
> Robert P. J. Day Ottawa, Ontario, CANADA
> http://crashcourse.ca
>
> Twitter: http://twitter.com/rpjday
> LinkedIn: http://ca.linkedin.com/in/rpjday
> ========================================================================
>
> --
> _______________________________________________
> yocto mailing list
> [email protected]
> https://lists.yoctoproject.org/listinfo/yocto
--
"Do or do not. There is no try"
Yoda Master
--
_______________________________________________
yocto mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/yocto
