summaryrefslogtreecommitdiffstats
path: root/meta-phosphor/classes/image-overlay.bbclass
Commit message (Collapse)AuthorAgeFilesLines
* image-overlay: Include initramfs in kernel FITRick Altherr2017-01-251-15/+3
| | | | | | | | Instead of packaging the initramfs separately in the flash image, use the FIT image that includes kernel+fdt+initramfs. Change-Id: I0a3315cfc635acbfaf7b603f5dca7da1ddeae1c1 Signed-off-by: Rick Altherr <raltherr@google.com>
* Consolidate flash image generationRick Altherr2017-01-101-0/+84
| | | | | | | | | | | | | | | | | Before c7248eb11c and 794bd3d4ac, flash image generation was split between obmc-phosphor-image_types_uboot.bbclass and image-overlay.bbclass. This was because generate_flash() relied on calling oe_mkimage() which was also defined in obmc-phosphor-image_types_uboot.bbclass. With that dependency removed, all of the flash image generation can now be consolidated into image-overlay.bbclass. This location makes more sense as the .uboot image type is for generating U-Boot legacy ramdisks while the overlay image type is specifically for OpenBMC and its flash layout. obmc-phopshor-image_types_uboot.bbclass is now empty and has been removed. Change-Id: Idcf38d3ef6f419780a7c54c77f1195bf3b5f5667 Signed-off-by: Rick Altherr <raltherr@google.com>
* Remove unused INITRD variableRick Altherr2016-12-191-1/+0
| | | | | Change-Id: I18777b815ca119dc8451e2378356a0f264717e9b Signed-off-by: Rick Altherr <raltherr@google.com>
* Create a phosphor-specific initramfsRick Altherr2016-12-191-1/+1
| | | | | | | | | | | | OpenBMC has been using a .bbappend to add/remove packages from core-image-minimal-initramfs. Doing so keeps the recipe and initramfs image name as core-image-minimal-initramfs which is misleading as it now is very much phosphor-specific. Instead, make a new obmc-phosphor-initramfs recipe and image that is patterned after core-image-minimal-initramfs. Change-Id: Ieca2268eff01bb61cc0d25a1cbc1a6f5fadb6d2c Signed-off-by: Rick Altherr <raltherr@google.com>
* image-overlay: depend on do_image_completePatrick Williams2016-06-241-2/+2
| | | | | | | Per Yocto commit 3341f3fb, we should depend on do_image_complete instead of do_rootfs for the initrd images. Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
* Don't inherit image-overlay by defaultBrad Bishop2016-02-291-3/+5
| | | | | | | | | | | This attempts to address a race condition in the build where we attempt to build a complete flash image before all the sub-images are available (specifically the initramfs image). Any classes in IMAGE_CLASSES are inherited by all image recipes, including the initramfs image. OE-Core's live/hddimg recipes address this by pulling in the class configuration in recipe scope, rather than global scope. Copy that behavior here.
* openbmc: Switch RW FS from ext4 to jffs2Andrew Jeffery2016-02-241-1/+1
| | | | Signed-off-by: Andrew Jeffery <andrew@aj.id.au>
* Create image class image-overlay and move phosphor to use itMilton D. Miller II2016-01-281-0/+18
This commit creates a new class image-overlay based on how the image-live class is structured. It takes parameters for the base and overlayed file system types but the initfs only support ext4 over squashfs presently. It then moves invoking the generation of the flash image from a post image creation command to a separate task invoked from the overlay image so that building the initramfs image by itself does not try to create a flash image. Signed-off-by: Milton Miller <miltonm@us.ibm.com>
OpenPOWER on IntegriCloud