diff options
author | Stefan Stanacar <stefanx.stanacar@intel.com> | 2014-03-30 17:47:34 +0300 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2014-03-31 17:54:35 +0100 |
commit | dea237ccd9407288cd3a73e1deca270619dd6d4a (patch) | |
tree | 2219c29169a4723846e27ab0d09c7b690a86f084 /meta/recipes-extended/images/core-image-lsb.bb | |
parent | 39fcab00cd3b85d40966689e31b4c7748f630739 (diff) | |
download | openembedded-core-dea237ccd9407288cd3a73e1deca270619dd6d4a.tar.gz openembedded-core-dea237ccd9407288cd3a73e1deca270619dd6d4a.tar.bz2 openembedded-core-dea237ccd9407288cd3a73e1deca270619dd6d4a.zip |
recipes-extended: add master image for testing purposes
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]
Signed-off-by: Stefan Stanacar <stefanx.stanacar@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-extended/images/core-image-lsb.bb')
0 files changed, 0 insertions, 0 deletions