From: Stefan Stanacar <stefanx.stanacar@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/3] Master image generation and hw testing
Date: Sun, 30 Mar 2014 17:47:32 +0300 [thread overview]
Message-ID: <cover.1396188987.git.stefanx.stanacar@intel.com> (raw)
Hello,
This is what I currently use for doing automated deployment
for a genericx86-64 image on NUC. More details on the commit
messages. There is nothing particular to genericx86-64,
it should work on any EFI-enabled device with gummiboot as bootloader.
Also see YB#1596 and it's sub-bug #5614 for a bit of background.
Cheers,
Stefan
V4: this is almost identical to the RFC sent but:
- squased the first two patches
- adress Otavio's comments - rename the class and use a constant for one
of the deploy commands
- cosmetic changes, mostly comments/typos, nothing functional
The following changes since commit 790cc61a754d156c15f77c95539e17ec4d9f2c41:
bitbake: user-manual-execution.xml: Added how BB processes curly braces. (2014-03-30 10:19:49 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib stefans/masterimage
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=stefans/masterimage
Stefan Stanacar (3):
initrdscripts: add install scripts with a second rootfs
recipes-extended: add master image for testing purposes
lib/oeqa: add a test target controller for EFI targets
meta/lib/oeqa/controllers/masterimage.py | 133 +++++++++++++
meta/lib/oeqa/runtime/ssh.py | 2 +
.../initrdscripts/files/init-install-efi-testfs.sh | 199 +++++++++++++++++++
.../initrdscripts/files/init-install-testfs.sh | 211 +++++++++++++++++++++
.../initramfs-live-install-efi-testfs_1.0.bb | 14 ++
.../initramfs-live-install-testfs_1.0.bb | 14 ++
.../images/core-image-testmaster-initramfs.bb | 19 ++
.../images/core-image-testmaster.bb | 18 ++
8 files changed, 610 insertions(+)
create mode 100644 meta/lib/oeqa/controllers/masterimage.py
create mode 100644 meta/recipes-core/initrdscripts/files/init-install-efi-testfs.sh
create mode 100644 meta/recipes-core/initrdscripts/files/init-install-testfs.sh
create mode 100644 meta/recipes-core/initrdscripts/initramfs-live-install-efi-testfs_1.0.bb
create mode 100644 meta/recipes-core/initrdscripts/initramfs-live-install-testfs_1.0.bb
create mode 100644 meta/recipes-extended/images/core-image-testmaster-initramfs.bb
create mode 100644 meta/recipes-extended/images/core-image-testmaster.bb
--
1.8.5.3
next reply other threads:[~2014-03-30 15:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-30 14:47 Stefan Stanacar [this message]
2014-03-30 14:47 ` [PATCH 1/3] initrdscripts: add install scripts with a second rootfs Stefan Stanacar
2014-03-30 14:47 ` [PATCH 2/3] recipes-extended: add master image for testing purposes Stefan Stanacar
2014-03-30 14:47 ` [PATCH 3/3] lib/oeqa: add a test target controller for EFI targets Stefan Stanacar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1396188987.git.stefanx.stanacar@intel.com \
--to=stefanx.stanacar@intel.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox