mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Barebox List <barebox@lists.infradead.org>
Subject: ubi: Make attaching UBI more convenient
Date: Fri, 26 Jun 2015 09:30:59 +0200	[thread overview]
Message-ID: <1435303867-12889-1-git-send-email-s.hauer@pengutronix.de> (raw)

Using UBI is a matter of using 'ubiattach' before UBI volumes can
be used. This makes it hard to use since the various autodetection
mechanisms can't be used. This series changes this. We introduce
predictable names for UBI devices and volumes and hook UBI attachment
into the mtd devices detect callback. This makes these commands possible:

# UBI attach nand0.root and mount to /mnt/nand0.root.ubi.root:
mount nand0.root.ubi.root

or:

# boot bootspec entry on an UBIFS found on the
# UBI volume 'root' on nand0.root:
boot nand0.root.ubi.root

or just:

# If there's UBI found on nand0.root then attach it:
detect nand0.root

Sascha

----------------------------------------------------------------
Sascha Hauer (8):
      commands: detect: use device_detect_by_name
      driver: detect: detect parent devices aswell
      blspec: Use device_detect_by_name
      ubi: Use preditable device names
      mtd: detect ubi devices automatically
      ubi: Lower 'already attached' message to debug level
      commands: mount: detect the device to be mounted
      ubi: Update documentation

 Documentation/user/ubi.rst | 44 +++++++++++++++-----------------------------
 commands/detect.c          |  5 +----
 commands/mount.c           |  2 ++
 common/blspec.c            |  9 +--------
 drivers/base/driver.c      | 25 ++++++++++++++++++++-----
 drivers/mtd/core.c         | 40 ++++++++++++++++++++++++++++++++++++++++
 drivers/mtd/ubi/build.c    |  9 +++------
 drivers/mtd/ubi/cdev.c     |  4 ++--
 8 files changed, 84 insertions(+), 54 deletions(-)

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2015-06-26  7:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-26  7:30 Sascha Hauer [this message]
2015-06-26  7:31 ` [PATCH 1/8] commands: detect: use device_detect_by_name Sascha Hauer
2015-06-26  7:31 ` [PATCH 2/8] driver: detect: detect parent devices aswell Sascha Hauer
2015-06-26  7:31 ` [PATCH 3/8] blspec: Use device_detect_by_name Sascha Hauer
2015-06-26  7:31 ` [PATCH 4/8] ubi: Use preditable device names Sascha Hauer
2015-06-26  7:31 ` [PATCH 5/8] mtd: detect ubi devices automatically Sascha Hauer
2015-06-26  7:31 ` [PATCH 6/8] ubi: Lower 'already attached' message to debug level Sascha Hauer
2015-06-26  7:31 ` [PATCH 7/8] commands: mount: detect the device to be mounted Sascha Hauer
2015-06-26  7:31 ` [PATCH 8/8] ubi: Update documentation Sascha Hauer

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=1435303867-12889-1-git-send-email-s.hauer@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@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