All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julius Werner <jwerner@chromium.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3 0/2] fit: Image node compression
Date: Fri,  3 May 2019 14:26:45 -0700	[thread overview]
Message-ID: <20190503212647.120603-1-jwerner@chromium.org> (raw)

This patch series adds compression support for non-kernel FIT image
nodes (e.g. FDTs). The first patch adds the compression support
itself, the second adds a new feature to compatible string matching
that allows it to be useful with compressed FDTs.

Sandbox-tested with FIT images with and without compressed FDTs, with
and without overlays, in both compatible string matching and direct
config selection modes. Also expanded the test_fit pytest to include a
case with compressed kernel, FDT and ramdisk.

Julius Werner (2):
  fit: Support compression for non-kernel components (e.g. FDT)
    - Changes for v2:
      - Changed from only supporting compressed FDTs to supporting all
	non-kernel image node types.
  fit: Support compat string property in configuration node

 common/image-fit.c | 140 +++++++++++++++++++++++++++------------------
 1 file changed, 83 insertions(+), 57 deletions(-)

-- 
2.20.1

             reply	other threads:[~2019-05-03 21:26 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-03 21:26 Julius Werner [this message]
2019-05-03 21:26 ` [U-Boot] [PATCH v3 1/2] fit: Support compression for non-kernel components (e.g. FDT) Julius Werner
2019-05-13 23:34   ` Simon Glass
2019-05-14  1:12     ` Julius Werner
2019-05-14 10:55       ` Simon Glass
2019-05-14 11:16         ` Simon Goldschmidt
2019-05-15  3:11           ` Simon Glass
2019-05-15 22:29             ` Julius Werner
2019-05-03 21:26 ` [U-Boot] [PATCH v3 2/2] fit: Support compat string property in configuration node Julius Werner
2019-05-13 23:35   ` Simon Glass
2019-05-14  1:15     ` Julius Werner
2019-05-14 10:56       ` Simon Glass

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=20190503212647.120603-1-jwerner@chromium.org \
    --to=jwerner@chromium.org \
    --cc=u-boot@lists.denx.de \
    /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.