From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: Alexander Kanevskiy <kad@kad.name>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2 1/3] bmap-tools: initial commit, version 3.2
Date: Mon, 2 May 2016 08:43:00 +0300 [thread overview]
Message-ID: <20160502054300.GA6563@linux.intel.com> (raw)
In-Reply-To: <CANFkWpkNKn84OYakUYmD7piyyK=9TLbf=+yM+Zy2mJnqg=wdjA@mail.gmail.com>
On Fri, Apr 29, 2016 at 11:38:38AM +0300, Alexander Kanevskiy wrote:
> On Fri, Apr 29, 2016 at 7:55 AM, Paul Eggleton <
> paul.eggleton@linux.intel.com> wrote:
>
> > On Fri, 29 Apr 2016 01:07:56 Alexander Kanevskiy wrote:
> > > On Wed, Apr 27, 2016 at 12:36 PM, Ed Bartosh <ed.bartosh@linux.intel.com
> > >
> > >
> > > wrote:
> > > > 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".
> > > >
> > > > [YOCTO #9414]
> > > >
> > > > Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com>
> > >
> > > better to use recipe that would create in deploy/tools standalone version
> > > of the tool.
> > > Otherwise, there is no easy way for user to utilize generated bmap files.
> >
> > You both probably have had notification already, but just to close the
> > loop I
> > found the issue with the do_deploy version, see the comments on bug 9414:
> >
> > https://bugzilla.yoctoproject.org/show_bug.cgi?id=9414
> >
> >
> Thank you Paul for your help! Your fix mentioned in the bug for do_depoly
> is indeed the best solution.
>
OK. I'll add this functionality back in a separate patch.
--
Regards,
Ed
next prev parent reply other threads:[~2016-05-02 8:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 9:36 [PATCH v2 0/3] bmaptool support Ed Bartosh
2016-04-27 9:36 ` [PATCH v2 1/3] bmap-tools: initial commit, version 3.2 Ed Bartosh
2016-04-28 22:07 ` Alexander Kanevskiy
2016-04-29 4:55 ` Paul Eggleton
2016-04-29 8:38 ` Alexander Kanevskiy
2016-05-02 5:43 ` Ed Bartosh [this message]
2016-04-27 9:36 ` [PATCH v2 2/3] image types: add bmap generation option Ed Bartosh
2016-04-27 9:36 ` [PATCH v2 3/3] selftest: add bmap test Ed Bartosh
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=20160502054300.GA6563@linux.intel.com \
--to=ed.bartosh@linux.intel.com \
--cc=kad@kad.name \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
/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.