From: Patrick Ohly <patrick.ohly@intel.com>
To: Robert Berger <yocto.user.mailinglist@gmail.com>, yocto@yoctoproject.org
Subject: Re: minimize size of SW update bundle
Date: Thu, 19 Oct 2017 09:18:51 +0200 [thread overview]
Message-ID: <1508397531.25153.72.camel@intel.com> (raw)
In-Reply-To: <8653269a-f4c0-e7f4-1393-7c77ad18502d@gmail.com>
On Tue, 2017-10-17 at 16:12 +0300, Robert Berger wrote:
> Hi,
>
> Imagine you have only a limited bandwidth to your devices available
> for
> SW update. So you would like to minimize what's uploaded (over the
> air)
> to your devices.
>
> How would you do this with yocto?
>
> [1] and [2] might be able to do incremental updates,
Both can indeed do it.
> Like how would you get a diff between two release builds...
>
> [1] https://wiki.yoctoproject.org/wiki/Meta-swupd
With meta-swupd, set SWUPD_DELTAPACK_VERSIONS to generate binary diffs
against certain older releases. In addition, a single archive gets
created with just the right content for updating from the older
releases to the current one (= better compression, less GET requests).
> [2] https://github.com/advancedtelematic/meta-updater
That's basically OSTree. See https://ostree.readthedocs.io/en/latest/ma
nual/repository-management/#derived-data-static-deltas-and-the-summary-
file for instructions on generating deltas.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
prev parent reply other threads:[~2017-10-19 7:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-17 5:28 Release Candidate Build for yocto-2.4.rc3 now available pokybuild
2017-10-17 13:12 ` minimize size of SW update bundle Robert Berger
2017-10-17 13:28 ` Alexander Kanavin
2017-10-17 14:11 ` Marc Ferland
2017-10-18 20:34 ` Paul Eggleton
2017-10-19 7:18 ` Patrick Ohly [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=1508397531.25153.72.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=yocto.user.mailinglist@gmail.com \
--cc=yocto@yoctoproject.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.