From: Stefan Stanacar <stefanx.stanacar@intel.com>
To: poky@yoctoproject.org
Subject: [RFC PATCH 0/4] Master image generation and testing
Date: Sun, 9 Mar 2014 20:49:15 +0200 [thread overview]
Message-ID: <cover.1394390131.git.stefanx.stanacar@intel.com> (raw)
Hello,
This is what I currently use for doing completely automated testing
on a genericx86-64 image installed on NUC. More details on the commit
messages.
This series is sent against stefans/gummiboot branch from poky-contrib (
as gummiboot is required as it obeys the LoadEntryOneShot EFI variable).
The first patch is just for build convenience here, not to get merged
(or one has to configure his kernel manually or with the
various ways available). It's my opinion that those EFI options should
go into the default cfg/efi fragment. (CONFIG_EFI_STUB is at least
required by gummiboot to actually boot).
The second patch is for review/diff convenience of the install-efi.sh script
Also see YB#1596 and it's sub-bug #5614 for a bit of background.
Any comments, questions, most welcome.
Cheers,
Stefan
Please review the following changes for suitability for inclusion. If you have
any objections or suggestions for improvement, please respond to the patches. If
you agree with the changes, please provide your Acked-by.
The following changes since commit 1444a02c93e9e64a82f4a9ba80dc693e2b5e56db:
classes: Add gummiboot class (2014-03-09 17:11:28 +0200)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib stefans/masterimage
http://git.yoctoproject.org/cgit.cgi//log/?h=stefans/masterimage
Stefan Stanacar (4):
linux-yocto_3.10.bbappend: EFI kernel config for easier building
meta-yocto-bsp: copy install scripts from meta (dummy commit)
meta-yocto-bsp: add master image for testing purposes
meta-yocto-bsp: add a controller for EFI targets where a master image
is running
meta-yocto-bsp/lib/oeqa/controllers/__init__.py | 0
meta-yocto-bsp/lib/oeqa/controllers/masterimage.py | 88 +++++++++
.../images/core-image-testmaster-initramfs.bb | 20 ++
.../recipes-core/images/core-image-testmaster.bb | 16 ++
.../initrdscripts/files/init-install-efi-testfs.sh | 199 +++++++++++++++++++
.../initrdscripts/files/init-install-testfs.sh | 211 +++++++++++++++++++++
.../initramfs-live-install-efi-testfs_1.0.bb | 20 ++
.../initramfs-live-install-testfs_1.0.bb | 20 ++
.../recipes-kernel/linux/files/efioptions.cfg | 4 +
.../recipes-kernel/linux/linux-yocto_3.10.bbappend | 5 +
meta/lib/oeqa/runtime/ssh.py | 2 +
11 files changed, 585 insertions(+)
create mode 100644 meta-yocto-bsp/lib/oeqa/controllers/__init__.py
create mode 100644 meta-yocto-bsp/lib/oeqa/controllers/masterimage.py
create mode 100644 meta-yocto-bsp/recipes-core/images/core-image-testmaster-initramfs.bb
create mode 100644 meta-yocto-bsp/recipes-core/images/core-image-testmaster.bb
create mode 100644 meta-yocto-bsp/recipes-core/initrdscripts/files/init-install-efi-testfs.sh
create mode 100644 meta-yocto-bsp/recipes-core/initrdscripts/files/init-install-testfs.sh
create mode 100644 meta-yocto-bsp/recipes-core/initrdscripts/initramfs-live-install-efi-testfs_1.0.bb
create mode 100644 meta-yocto-bsp/recipes-core/initrdscripts/initramfs-live-install-testfs_1.0.bb
create mode 100644 meta-yocto-bsp/recipes-kernel/linux/files/efioptions.cfg
--
1.8.5.3
next reply other threads:[~2014-03-09 18:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-09 18:49 Stefan Stanacar [this message]
2014-03-09 18:49 ` [RFC PATCH 1/4] linux-yocto_3.10.bbappend: EFI kernel config for easier building Stefan Stanacar
2014-03-09 18:49 ` [RFC PATCH 2/4] meta-yocto-bsp: copy install scripts from meta (dummy commit) Stefan Stanacar
2014-03-09 18:49 ` [RFC PATCH 3/4] meta-yocto-bsp: add master image for testing purposes Stefan Stanacar
2014-03-09 18:49 ` [RFC PATCH 4/4] meta-yocto-bsp: add a controller for EFI targets where a master image is running Stefan Stanacar
-- strict thread matches above, loose matches on Subject: below --
2014-03-20 16:29 [RFC PATCH 0/4] Master image generation and testing 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.1394390131.git.stefanx.stanacar@intel.com \
--to=stefanx.stanacar@intel.com \
--cc=poky@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.