summaryrefslogtreecommitdiffstats
path: root/meta/recipes-extended/images/core-image-testmaster.bb
Commit message (Collapse)AuthorAgeFilesLines
* core-image-testmaster.bb: add bzip2 to imageCorneliu Stoicescu2014-06-131-1/+1
| | | | | | | | | | | YB: #6375 Some test image fstypes require bzip2 decompression. (From OE-Core rev: 7b81fce3a80f7a1b94015a1da95d2349dac577ab) Signed-off-by: Corneliu Stoicescu <corneliux.stoicescu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* recipes-extended: add master image for testing purposesStefan Stanacar2014-03-311-0/+18
Add a custom recipe with custom initramfs and installers, that makes it easy to deploy a master image for testing purposes. We need a master image running on the target hardware, that should be a known good build, with a set of utilities installed so that we use it to deploy the images under test. This core-image-testmaster recipe isn't a requirement per se, any image can be used as long as the required conditions are met. The test code assumes: - that the device has a second rootfs labeled as testrootfs - it has a properly configured bootloader entry (called test) for the second kernel and rootfs - the master image has a /etc/masterimage file so it can differentiate between master and test images - the master image has tar, mount, bash (basically the normal linux utilities not the busybox ones) [YOCTO #5614] (From OE-Core rev: dea237ccd9407288cd3a73e1deca270619dd6d4a) Signed-off-by: Stefan Stanacar <stefanx.stanacar@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>