From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH] bmap-tools: v3.2 (initial commit)
Date: Mon, 3 Aug 2015 11:37:54 +0300 [thread overview]
Message-ID: <1438591074-14488-1-git-send-email-ed.bartosh@linux.intel.com> (raw)
Bmap-tools - tools to generate block map (AKA bmap) and flash images
using bmap. Bmaptool is a generic tool for creating the block map
(bmap) for a file and copying files using the block map.
The idea is that large file containing unused blocks, like raw system
image files, can be copied or flashed a lot faster with bmaptool than
with traditional tools like "dd" or "cp".
This package provides Python API, which can be used to generate
bmaps for Yocto images produced by bitbake and wic.
Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com>
---
meta/recipes-extended/bmap-tools/bmap-tools_3.2.bb | 15 +++++++++++++++
1 file changed, 15 insertions(+)
create mode 100644 meta/recipes-extended/bmap-tools/bmap-tools_3.2.bb
diff --git a/meta/recipes-extended/bmap-tools/bmap-tools_3.2.bb b/meta/recipes-extended/bmap-tools/bmap-tools_3.2.bb
new file mode 100644
index 0000000..79a2aa9
--- /dev/null
+++ b/meta/recipes-extended/bmap-tools/bmap-tools_3.2.bb
@@ -0,0 +1,15 @@
+DESCRIPTION = "Tools to generate block map (AKA bmap) and flash images using bmap."
+HOMEPAGE = "http://source.tizen.org/documentation/reference/bmaptool/bmap-tools-project"
+SECTION = "console/tools"
+LICENSE = "GPLv2.0"
+LIC_FILES_CHKSUM = "file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263"
+
+SRC_URI = "ftp://ftp.infradead.org/pub/${BPN}/${BPN}-${PV}.tgz"
+SRC_URI[md5sum] = "92cdad1cb4dfa0cca7176c8e22752616"
+SRC_URI[sha256sum] = "cc6c7f7dc0a37e2a32deb127308e24e6c4b80bfb54f3803c308efab02bf2d434"
+
+RDEPENDS_${PN} = "bzip2 gzip lzop pigz python tar xz"
+
+inherit setuptools
+
+BBCLASSEXTEND = "native"
--
2.1.4
reply other threads:[~2015-08-03 8:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1438591074-14488-1-git-send-email-ed.bartosh@linux.intel.com \
--to=ed.bartosh@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