* is there really an "INITRD_IMAGE" variable?
@ 2016-06-22 10:03 Robert P. J. Day
2016-06-22 12:57 ` Daniel.
0 siblings, 1 reply; 4+ messages in thread
From: Robert P. J. Day @ 2016-06-22 10:03 UTC (permalink / raw)
To: Yocto discussion list
(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
========================================================================
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: is there really an "INITRD_IMAGE" variable?
2016-06-22 10:03 is there really an "INITRD_IMAGE" variable? Robert P. J. Day
@ 2016-06-22 12:57 ` Daniel.
2016-06-22 14:20 ` Robert P. J. Day
0 siblings, 1 reply; 4+ messages in thread
From: Daniel. @ 2016-06-22 12:57 UTC (permalink / raw)
To: Robert P. J. Day; +Cc: Yocto discussion list
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 <rpjday@crashcourse.ca>:
>
> (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
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
--
"Do or do not. There is no try"
Yoda Master
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: is there really an "INITRD_IMAGE" variable?
2016-06-22 12:57 ` Daniel.
@ 2016-06-22 14:20 ` Robert P. J. Day
2016-06-22 14:29 ` Daniel.
0 siblings, 1 reply; 4+ messages in thread
From: Robert P. J. Day @ 2016-06-22 14:20 UTC (permalink / raw)
To: Daniel.; +Cc: Yocto discussion list
On Wed, 22 Jun 2016, Daniel. wrote:
> 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]$
it looks like there was a shift from INITRD_IMAGE to one of
INITRD_IMAGE_VM or INITRD_IMAGE_LIVE on feb 24, 2016 in this commit in
oe-core:
commit e38c94d6bf83ed3ca7f046d9503e81b927487bf2
Author: Robert Yang <liezhi.yang@windriver.com>
Date: Wed Feb 24 01:23:58 2016 -0800
syslinux.bbclass: make vm and live can be built together
* The vm image(hdddirect, vmdk, qcow2, vdi) and live image (hddimg, iso)
couldn't be built together because the following vars settings are
conflicted:
- SYSLINUX_ROOT (/dev/sda2 vs /dev/ram0)
- LABELS (boot vs boot install)
- INITRD (None vs live install)
- SYSLINUX_CFG (see above)
Introduce new vars (SYSLINUX_ROOT_VM/_LIVE, the samilar to others) to
make them can work together, now we can build all of them together:
IMAGE_FSTYPES += "live iso hddimg hdddirect vmdk qcow2 vdi"
* Use SYSLINUX_CFG rather than SYSLINUXCFG to keep align with others
SYSLINUX vars.
* The SYSLINUX_TIMEOUT had been set, but it didn't work since
AUTO_SYSLINUXMENU wasn't set, this would cause confusions, so also set
AUTO_SYSLINUXMENU.
* Move SYSLINUX_PROMPT and SYSLINUX_TIMEOUT to syslinux.bbclass rather
than in separate classes since they are the same.
* Set SYSLINUX_TIMEOUT to 50 to have a unique timeout for syslinux.
[YOCTO #9161]
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
and i guess someone just didn't notice the remaining references to
INITRD_IMAGE.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: is there really an "INITRD_IMAGE" variable?
2016-06-22 14:20 ` Robert P. J. Day
@ 2016-06-22 14:29 ` Daniel.
0 siblings, 0 replies; 4+ messages in thread
From: Daniel. @ 2016-06-22 14:29 UTC (permalink / raw)
To: Robert P. J. Day; +Cc: Yocto discussion list
It seem to be INITRD_IMAGE_LIVE now.
http://patchwork.openembedded.org/patch/116335/
2016-06-22 11:20 GMT-03:00 Robert P. J. Day <rpjday@crashcourse.ca>:
> On Wed, 22 Jun 2016, Daniel. wrote:
>
>> 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]$
>
> it looks like there was a shift from INITRD_IMAGE to one of
> INITRD_IMAGE_VM or INITRD_IMAGE_LIVE on feb 24, 2016 in this commit in
> oe-core:
>
> commit e38c94d6bf83ed3ca7f046d9503e81b927487bf2
> Author: Robert Yang <liezhi.yang@windriver.com>
> Date: Wed Feb 24 01:23:58 2016 -0800
>
> syslinux.bbclass: make vm and live can be built together
>
> * The vm image(hdddirect, vmdk, qcow2, vdi) and live image (hddimg, iso)
> couldn't be built together because the following vars settings are
> conflicted:
> - SYSLINUX_ROOT (/dev/sda2 vs /dev/ram0)
> - LABELS (boot vs boot install)
> - INITRD (None vs live install)
> - SYSLINUX_CFG (see above)
> Introduce new vars (SYSLINUX_ROOT_VM/_LIVE, the samilar to others) to
> make them can work together, now we can build all of them together:
>
> IMAGE_FSTYPES += "live iso hddimg hdddirect vmdk qcow2 vdi"
>
> * Use SYSLINUX_CFG rather than SYSLINUXCFG to keep align with others
> SYSLINUX vars.
>
> * The SYSLINUX_TIMEOUT had been set, but it didn't work since
> AUTO_SYSLINUXMENU wasn't set, this would cause confusions, so also set
> AUTO_SYSLINUXMENU.
>
> * Move SYSLINUX_PROMPT and SYSLINUX_TIMEOUT to syslinux.bbclass rather
> than in separate classes since they are the same.
>
> * Set SYSLINUX_TIMEOUT to 50 to have a unique timeout for syslinux.
>
> [YOCTO #9161]
>
> Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
> Signed-off-by: Ross Burton <ross.burton@intel.com>
>
> and i guess someone just didn't notice the remaining references to
> INITRD_IMAGE.
>
> rday
>
> --
>
> ========================================================================
> Robert P. J. Day Ottawa, Ontario, CANADA
> http://crashcourse.ca
>
> Twitter: http://twitter.com/rpjday
> LinkedIn: http://ca.linkedin.com/in/rpjday
> ========================================================================
>
--
"Do or do not. There is no try"
Yoda Master
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2016-06-22 14:29 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-06-22 10:03 is there really an "INITRD_IMAGE" variable? Robert P. J. Day
2016-06-22 12:57 ` Daniel.
2016-06-22 14:20 ` Robert P. J. Day
2016-06-22 14:29 ` Daniel.
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.