public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: claudius.heine.ext@siemens.com
To: isar-users@googlegroups.com
Cc: Claudius Heine <ch@denx.de>
Subject: [PATCH v3 0/5] UBI support
Date: Mon,  4 Feb 2019 16:54:49 +0100	[thread overview]
Message-ID: <20190204155454.27465-1-claudius.heine.ext@siemens.com> (raw)

From: Claudius Heine <ch@denx.de>

Hi,

here is the third version of the UBI support patchset. This patch
depends on merging the `Template system` patchset first.

Claudius

Changes from v2:

 - added fit image support patch
 - moved to new templating system
 - refactored `copy_boot_files` of isar-image-ubi

Changes from v1:
 
 - fixed license header
 - removed ubifs test since it is included in the ubi test
 - merged ubifs and ubi patchset
 - renamed qemusabrelite to nand-ubi-demo
 - added nand-ubi-demo to ci build
 - added some entries for ubi/ubifs support in manual

Claudius Heine (5):
  doc/user: added targz-img to image type list
  meta/classes: added ubifs-img class
  meta/classes: added ubi-img class
  meta/classes: added fit-img class for creation of fit images
  meta-isar: added nand-ubi-demo example to demonstrate UBI use

 doc/user_manual.md                            |  6 +-
 meta-isar/classes/ubi-ubifs-img.bbclass       | 10 ++++
 meta-isar/conf/local.conf.sample              |  1 +
 meta-isar/conf/machine/nand-ubi-demo.conf     | 13 +++++
 .../multiconfig/nand-ubi-demo-buster.conf     | 13 +++++
 .../images/files/fitimage.its.tmpl            | 58 +++++++++++++++++++
 .../images/files/ubinize.cfg.tmpl             | 17 ++++++
 .../recipes-core/images/isar-image-ubi.bb     | 40 +++++++++++++
 meta/classes/fit-img.bbclass                  | 49 ++++++++++++++++
 meta/classes/ubi-img.bbclass                  | 52 +++++++++++++++++
 meta/classes/ubifs-img.bbclass                | 44 ++++++++++++++
 scripts/ci_build.sh                           |  1 +
 12 files changed, 303 insertions(+), 1 deletion(-)
 create mode 100644 meta-isar/classes/ubi-ubifs-img.bbclass
 create mode 100644 meta-isar/conf/machine/nand-ubi-demo.conf
 create mode 100644 meta-isar/conf/multiconfig/nand-ubi-demo-buster.conf
 create mode 100644 meta-isar/recipes-core/images/files/fitimage.its.tmpl
 create mode 100644 meta-isar/recipes-core/images/files/ubinize.cfg.tmpl
 create mode 100644 meta-isar/recipes-core/images/isar-image-ubi.bb
 create mode 100644 meta/classes/fit-img.bbclass
 create mode 100644 meta/classes/ubi-img.bbclass
 create mode 100644 meta/classes/ubifs-img.bbclass

-- 
2.20.1


             reply	other threads:[~2019-02-04 15:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-04 15:54 claudius.heine.ext [this message]
2019-02-04 15:54 ` [PATCH v3 1/5] doc/user: added targz-img to image type list claudius.heine.ext
2019-02-04 15:54 ` [PATCH v3 2/5] meta/classes: added ubifs-img class claudius.heine.ext
2019-02-04 15:54 ` [PATCH v3 3/5] meta/classes: added ubi-img class claudius.heine.ext
2019-02-04 16:04   ` Claudius Heine
2019-02-04 15:54 ` [PATCH v3 4/5] meta/classes: added fit-img class for creation of fit images claudius.heine.ext
2019-02-04 15:54 ` [PATCH v3 5/5] meta-isar: added nand-ubi-demo example to demonstrate UBI use claudius.heine.ext

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=20190204155454.27465-1-claudius.heine.ext@siemens.com \
    --to=claudius.heine.ext@siemens.com \
    --cc=ch@denx.de \
    --cc=isar-users@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox