From: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH v2 0/7] poky-tiny improvements
Date: Wed, 11 Jan 2017 19:55:17 +0000 [thread overview]
Message-ID: <cover.1484164023.git.alejandro.hernandez@linux.intel.com> (raw)
This is the first set of patches meant to improve some of the characteristics
of poky-tiny, these patches are from or based on Tom Zanussi's work; includes
a new image recipe to be able to boot poky-tiny from initrd, along with
changes to be able to create it using bootimg-efi, make it compatible with
systemd-boot, and scripts to measure size of the image, kernel and modules.
The following changes since commit 7d5dec1b1f3d1580e10bf4f92ef4aac4edb5ee77:
gummiboot: Remove old gummiboot recipe, related class and wks file (2017-01-11 19:45:41 +0000)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib hsalejandro/tinymaster3
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=hsalejandro/tinymaster3
Alejandro Hernandez (3):
image-.bbclass: standarize usage of DEPLOY_DIR_IMAGE
core-image-tiny-initramfs: Fix error message shown after a successful
initrd boot
systemd-boot.bbclass: Fix SYSYTEMD_BOOT_CFG creation
Tom Zanussi (4):
image-live-artifacts: Add support for creating image artifacts only
wic: Look for image artifacts in a common location
core-image-tiny-initramfs: Add and image creating image artifacts only
tiny scripts improvements: python3 fixes and new tool ksum
meta/classes/image-live-artifacts.bbclass | 40 +++++
meta/classes/image-live.bbclass | 18 +--
meta/classes/image-vm.bbclass | 12 +-
meta/classes/image.bbclass | 3 +
meta/classes/image_types.bbclass | 4 +-
meta/classes/systemd-boot.bbclass | 3 +
meta/lib/oeqa/selftest/wic.py | 2 +-
.../images/core-image-tiny-initramfs.bb | 42 ++++++
scripts/lib/wic/plugins/source/bootimg-efi.py | 28 +++-
.../lib/wic/plugins/source/isoimage-isohybrid.py | 21 ++-
scripts/tiny/ksize.py | 17 ++-
scripts/tiny/ksum.py | 168 +++++++++++++++++++++
12 files changed, 323 insertions(+), 35 deletions(-)
create mode 100644 meta/classes/image-live-artifacts.bbclass
create mode 100644 meta/recipes-core/images/core-image-tiny-initramfs.bb
create mode 100755 scripts/tiny/ksum.py
--
2.6.6
next reply other threads:[~2017-01-11 19:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 19:55 Alejandro Hernandez [this message]
2017-01-11 19:55 ` [PATCH v2 1/7] image-live-artifacts: Add support for creating image artifacts only Alejandro Hernandez
2017-01-12 12:52 ` Ylinen, Mikko
2017-01-12 22:34 ` Alejandro Hernandez
2017-01-11 19:55 ` [PATCH v2 2/7] wic: Look for image artifacts in a common location Alejandro Hernandez
2017-01-11 19:55 ` [PATCH 3/7] image-.bbclass: standarize usage of DEPLOY_DIR_IMAGE Alejandro Hernandez
2017-01-12 17:10 ` Burton, Ross
2017-01-12 18:41 ` Alejandro Hernandez
2017-01-11 19:55 ` [PATCH v2 4/7] core-image-tiny-initramfs: Add and image creating image artifacts only Alejandro Hernandez
2017-01-11 19:55 ` [PATCH 5/7] core-image-tiny-initramfs: Fix error message shown after a successful initrd boot Alejandro Hernandez
2017-01-11 19:55 ` [PATCH v2 6/7] tiny scripts improvements: python3 fixes and new tool ksum Alejandro Hernandez
2017-01-11 19:55 ` [PATCH 7/7] systemd-boot.bbclass: Fix SYSYTEMD_BOOT_CFG creation Alejandro Hernandez
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.1484164023.git.alejandro.hernandez@linux.intel.com \
--to=alejandro.hernandez@linux.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