summaryrefslogtreecommitdiff
path: root/meta/recipes-core/images/core-image-minimal-initramfs.bb
Commit message (Collapse)AuthorAgeFilesLines
* Hob: Modify Image DescriptionsElizabeth Flanagan2012-04-061-3/+3
| | | | | | | | Fixes [YOCTO #2227] I've updated the image descriptions per the bug description. Signed-off-by: Elizabeth Flanagan <elizabeth.flanagan@intel.com>
* core-image-foo: add description to each image bb fileShane Wang2012-01-241-0/+3
| | | | | | Add DESCRIPTION to each image bb file according to poky reference manual for Hob2 use later. Signed-off-by: Shane Wang <shane.wang@intel.com>
* bitbake.conf, core-image-minimal-initramfs: add INITRAMFS_FSTYPESDmitry Eremin-Solenikov2011-12-161-1/+1
| | | | | | | | | | | | | | Initramfs images don't benefit from usual IMAGE_FSTYPES overrides. The only sane values for them are "cpio.XXX". If IMAGE_FSTYPES is set to include 'live', building core-image-minimal-initramfs can result in build error, if the image is built before the kernel. To stop initramfs images from responding on IMAGE_FSTYPES settings, but still allow users/developers to override defaults (e.g. to generate "cpio.lzma" initramfs), introduce INITRAMFS_FSTYPES variable, by default set to "cpio.gz". Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* core-image-minimal-initramfs: force IMAGE_FSTYPESPaul Eggleton2011-11-071-0/+1
| | | | | | | | | | | | | If the user has set their own value for IMAGE_FSTYPES, they may have disabled the cpio.gz image type, preventing the initramfs from being produced in the format that image-live.bbclass expects; so force IMAGE_FSTYPES to cpio.gz within the initramfs image recipe. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Prepend cpio.gz instead Signed-off-by: Saul Wold <sgw@linux.intel.com>
* Prevent IMAGE_FEATURES from contaminating initrdDarren Hart2011-09-161-0/+3
| | | | | | | | | | Set IMAGE_FEATURES="" in core-image-initramfs to prevent the setting of things like EXTRA_IMAGE_FEATURES in local.conf from contaminating the initrd with features meant for the rootfs. Suggested-by: Richard Purdie <richardpurdie@linuxfoundation.org> Signed-off-by: Darren Hart <dvhart@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* IMAGE_ROOTFS_SIZE CleanupSaul Wold2011-05-251-0/+2
| | | | | | | | | | | | | | This basic cleanup removes the _ext2/3 overrides from places they no longer belong since they did not allow further overrides. In doing this the core-image-minimal* recipes can now set a reasonably small rootfs so that it's a realistic size for minimal. The new default for minimal is 8M and will be adujsted upward by the IMAGE_OVERHEAD_FACTOR (default of 1.3). This also fixes the ROOTFS_SIZE usage in the IMAGE_CMD_<fstype> code Signed-off-by: Saul Wold <sgw@linux.intel.com>
* Rename poky-image.bbclass to core-image.bbclassRichard Purdie2011-04-201-1/+1
| | | | Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Rename poky-image-* -> core-image-* and task-poky-* -> task-core-*Richard Purdie2011-04-201-0/+10
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>