From: YourName <andrea.adami@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-handheld][PATCH 2/2] initramfs-mininit-klibc-image: initial commit
Date: Fri, 23 May 2014 01:24:05 +0200 [thread overview]
Message-ID: <1400801045-14912-2-git-send-email-email@gmail.com> (raw)
In-Reply-To: <1400801045-14912-1-git-send-email-email@gmail.com>
From: Andrea Adami <andrea.adami@gmail.com>
This cpio does the job of finding and loop-mounting the rootfs file.
See https://github.com/pcercuei/mininit
Signed-off-by: Andrea Adami <andrea.adami@gmail.com>
---
.../images/initramfs-mininit-klibc-image.bb | 22 ++++++++++++++++++++++
1 file changed, 22 insertions(+)
create mode 100644 recipes-bsp/images/initramfs-mininit-klibc-image.bb
diff --git a/recipes-bsp/images/initramfs-mininit-klibc-image.bb b/recipes-bsp/images/initramfs-mininit-klibc-image.bb
new file mode 100644
index 0000000..18aad75
--- /dev/null
+++ b/recipes-bsp/images/initramfs-mininit-klibc-image.bb
@@ -0,0 +1,22 @@
+SUMMARY = "Initramfs image for mininit kernel"
+DESCRIPTION = "This image provides mininit (helper for booting loop images)."
+LICENSE = "MIT"
+LIC_FILES_CHKSUM = "file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
+
+IMAGE_FSTYPES = "${INITRAMFS_FSTYPES}"
+
+# avoid circular dependencies
+EXTRA_IMAGEDEPENDS = ""
+
+# We really need just kexecboot, kexec and ubiattach
+IMAGE_INSTALL = "mininit-klibc"
+
+# Do not pollute the initrd image with rootfs features
+IMAGE_FEATURES = ""
+
+IMAGE_LINGUAS = ""
+
+FEED_DEPLOYDIR_BASE_URI = ""
+LDCONFIGDEPEND = ""
+
+inherit image
--
1.9.1
prev parent reply other threads:[~2014-05-22 23:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 23:24 [meta-handheld][PATCH 1/2] mininit: initial commit of v. 1.1.0 YourName
2014-05-22 23:24 ` YourName [this message]
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=1400801045-14912-2-git-send-email-email@gmail.com \
--to=andrea.adami@gmail.com \
--cc=openembedded-devel@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 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.