From: Subodh Nijsure <snijsure@grid-net.com>
To: mtd <linux-mtd@lists.infradead.org>
Subject: Comparing UBI volumes to generate patch for upgrades
Date: Wed, 01 Feb 2012 10:31:35 -0800 [thread overview]
Message-ID: <4F298507.5010600@grid-net.com> (raw)
Hi,
I am are working on a embedded industrial product that uses UBIFS, but
we have limitation on amount of data this product can download per year.
So we are trying to figure out how to optimise size of upgrade package.
one option is use VCDIFF/bsdif or variation there-of and generate a
binary diff package.
option 2 is write a tool that compares UBI volume layout for revision 1
and UBI volume layout for revision 2 and then send that difference,
along the lines of what is outlined in the paper @
http://www.icmu.org/icmu2010/Papers/3-1.pdf
We are just getting started writing a tool to compare UBI volumes, but I
want to send out querry to UBI experts to see if there are some
fundamental issues with UBI that would make comparing UBI volumes and
applying such a patch would be a non-starter.
If we do come up with a "decent" enough tool that can compare UBI
volumes will certainly share it.
-Sam
next reply other threads:[~2012-02-01 18:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 18:31 Subodh Nijsure [this message]
2012-02-03 9:18 ` Comparing UBI volumes to generate patch for upgrades Artem Bityutskiy
2012-02-03 23:14 ` Subodh Nijsure
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=4F298507.5010600@grid-net.com \
--to=snijsure@grid-net.com \
--cc=linux-mtd@lists.infradead.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